We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the release of psycopg3 and its async capabilities, isn't this wrapper for the good-old synchronous psycopg2 unnecessary anymore?
At least I'd expect aiopg to mention its relation with psycopg3 and maybe declare sunset?
During the timespan where other libraries that could rely on aiopg won't yet move to psycopg3, maybe aiopg2 should become a thin wrapper for psycopg3? E.g. SQLAlchemy won't support psycopg3 until their 2.0 release https://github.com/sqlalchemy/sqlalchemy/milestone/88
No response
The text was updated successfully, but these errors were encountered:
One problem with psycopg3 is that does not work with PyPy unfortunately
Sorry, something went wrong.
Isn't psycopg2 pypy support also a "best effort" / "community patches welcome" but somehow "not officially supported"?
No branches or pull requests
Is your feature request related to a problem?
With the release of psycopg3 and its async capabilities, isn't this wrapper for the good-old synchronous psycopg2 unnecessary anymore?
Describe the solution you'd like
At least I'd expect aiopg to mention its relation with psycopg3 and maybe declare sunset?
Describe alternatives you've considered
During the timespan where other libraries that could rely on aiopg won't yet move to psycopg3, maybe aiopg2 should become a thin wrapper for psycopg3? E.g. SQLAlchemy won't support psycopg3 until their 2.0 release https://github.com/sqlalchemy/sqlalchemy/milestone/88
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: