The problem is that currently only the entire codebase can be migrated from
1.3 to 1.4, even though it can be extremely difficult or too long to do.
I suggest the following way of pinning dependencies:
sqlalchemy==1.3
sqlalchemy2==1.4 or sqlalchemy2==2.0
Then current codebase will continue to
hi there -
having a separate project name on pypi doesn't solve any issue that isn't
already solved by using version pinning - the "sqlalchemy" name on pypi is
already at 1.4. the only way to install 1.3 is by requesting "pip install
sqlalchemy < 1.4".
As you've probably seen, SQLAlchemy 1.4
Currently I'm on SQLAlchemy 1.3 and there is a lot of work I have to do to
migrate to 1.4 / 2.0. I think it's good idea to distribute 1.4 / 2.0
versions not only as "SQLAlchemy" project but as additional separate
"SQLAlchemy2" project too with initial 1.4 version and then 2.0. This will
give
