[SCRUM-146] chore: remove psycopg[binary] redundante, mantendo psycopg2-binary#34
Closed
[SCRUM-146] chore: remove psycopg[binary] redundante, mantendo psycopg2-binary#34
Conversation
Contributor
Collaborator
|
@degoNDL Só um ajuste antes do merge: o commit da branch está como SCRUM 146 / chore: ... e o nosso CI de commit check exige o formato SCRUM- (com hífen). Dá pra resolver rapidinho empurrando um commit vazio com a mensagem no padrão correto: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove o driver psycopg[binary] (psycopg3) do requirements.txt, mantendo apenas o psycopg2-binary que é efetivamente utilizado em runtime.
O SQLAlchemy seleciona o driver com base no prefixo da DATABASE_URL. Como a URL do projeto usa o formato postgresql://, o driver ativo é o psycopg2. O psycopg3 só seria selecionado com o prefixo postgresql+psycopg://, que não é utilizado em nenhum ponto do projeto. VALIDAÇÃO COM PYTEST APÓS A REMOÇÃO