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
Since psycopg 3 isn't slated to for GA with SQLAlchemy until their 2.0 release, most users of SQLAlchemy are still using v1.4 with psycopg2. For those of us on SQLAlchemy v1.4, it doesn't really make sense to write tests with this fixture package that requires psycopg 3. Would you be open to maintaining the v3.x line please so that we can continue to get feature upgrades and fixes without the psycopg2 requirement. I'd be happy to help maintain that branch if so.
What are the results
What are the expected results
The text was updated successfully, but these errors were encountered:
I'm open to backporting fixes to v3, but won't actively pursue it. Not sure if there's something major to get backported though 🤔
The actions and branch protection rules are in place for incoming Pull requests.
Thanks @fizyk. That was exactly what I was looking for. I assumed 3.1.2 was the end of the road for 3.x when I was looking at the changelog in main and I didn't think to look in pypi.
What action do you want to perform
Since
psycopg
3 isn't slated to for GA with SQLAlchemy until their 2.0 release, most users of SQLAlchemy are still using v1.4 withpsycopg2
. For those of us on SQLAlchemy v1.4, it doesn't really make sense to write tests with this fixture package that requirespsycopg
3. Would you be open to maintaining the v3.x line please so that we can continue to get feature upgrades and fixes without thepsycopg2
requirement. I'd be happy to help maintain that branch if so.What are the results
What are the expected results
The text was updated successfully, but these errors were encountered: