You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have moved from psycopg2[binary] to psycopg[binary] (Version 3.1.17 - Successor to psycopg2). But this package doesn't detects that. It has a fixed requirement of psycopg2 and therefore the installation fails.
django's backend
Switch to django's backend (django.db.backends.xxx), does the problem reproduce?
Can't test that as the installation fails.
Environment
Python Version: 3.10
Django Version: 4.2.7 & 4.2.9
Traceback
Post traceback here. If you prefer to avoid building psycopg2 from source, please install the PyPI err: 'psycopg2-binary' package instead.
Optional: SQL and parameters
Post SQL and parameters here, Pay attention to hiding private information.
N/A
The text was updated successfully, but these errors were encountered:
To clarify, even though the code change in #54 supports looking for pyscopg (v3) before falling back to psyopg2, if you specify django-db-connection-pool[postgresql] in your requiremetns, pip still wants to install pyscopg2 even if psycopg==3.* is also present in your requirements.txt file
However, if you spec django-db-connection-pool[psycopg3] then pip won't try to to install psycopg2 and will go for psycopg==3.* instead
Describe the bug
I have moved from psycopg2[binary] to psycopg[binary] (Version 3.1.17 - Successor to psycopg2). But this package doesn't detects that. It has a fixed requirement of psycopg2 and therefore the installation fails.
django's backend
Switch to django's backend (
django.db.backends.xxx
), does the problem reproduce?Can't test that as the installation fails.
Environment
Traceback
Post traceback here.
If you prefer to avoid building psycopg2 from source, please install the PyPI err: 'psycopg2-binary' package instead.
Optional: SQL and parameters
Post SQL and parameters here, Pay attention to hiding private information.
N/A
The text was updated successfully, but these errors were encountered: