Skip to content
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

Pin psycopg2-binary to ~2.8.0 #2275

Merged

Conversation

alexdutton
Copy link
Contributor

Django 1.11.x fails to connect to PostgreSQL databases when using psycopg2 2.9 onwards, due to a failing timezone-related assertion.

This also moves from psycopg2 to psycopg2-binary for Lando, which should have no external effect.

Closes #2274.

Django 1.11.x fails to connect to PostgreSQL databases when using
psycopg2 2.9 onwards, due to a failing timezone-related assertion.

This also moves from psycopg2 to psycopg2-binary for Lando, which should
have no external effect.

Closes openlibhums#2274.
@mauromsl
Copy link
Member

mauromsl commented Jun 24, 2021

Test this please (Jenkins) @Bbkctp

@mauromsl mauromsl self-requested a review June 24, 2021 15:03
Copy link
Member

@mauromsl mauromsl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @alexdutton

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.

Django <3.1 requires psycopg2 ~2.8.0, as >=2.9 is incompatible
3 participants