Skip to content

requirements-optionals: use psycopg2-binary #5969

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 8, 2018

Conversation

blueyed
Copy link
Contributor

@blueyed blueyed commented May 4, 2018

@tomchristie
Copy link
Member

Merging given that I trust both you folks on this, but what's the context?
When should you use the binary version vs. the regular version?
Is this documented someplace?

@tomchristie tomchristie merged commit 40d5985 into encode:master May 8, 2018
@kevin-brown
Copy link
Member

When should you use the binary version vs. the regular version?

The binary version provides wheels, and starting in 2.8 it will be the only package to provide wheels.

http://initd.org/psycopg/articles/2018/02/08/psycopg-274-released/

@xordoquy
Copy link
Collaborator

xordoquy commented May 8, 2018

TL;DR I saw psycopg2 fall back from SSL to clear version due to incompatible SSL versions.
http://initd.org/psycopg/articles/2018/02/08/psycopg-274-released/ would explain better than I would.
My experience was that openssl context was setup for 1.1+ and psycopg2 needed 1.0.x which was incompatible.

pchiquet pushed a commit to pchiquet/django-rest-framework that referenced this pull request Nov 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants