Hi, > 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 don't agree with this assessment. From my experience the main incompatibility is the url that has become immutable. Other than this most thing will work on 1.4 without changes. They will raise warnings that can be tackled right away or not, but it will keep working. Do you have some examples that prevent running 1.4 on a 1.3 codebase that make it long to adapt? Moving to the 2.x syntax can then be done gradually. I think having two package name will make the migration worse On Thursday, 10 June 2021 at 01:21:37 UTC+2 Marat Sharafutdinov wrote: > 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 work because "sqlalchemy" package > stays at version 1.3 but it will be possible to use SQLAlchemy 1.4 / 2.0 > additionally to migrate not whole codebase but part by part by importing > "sqlalchemy2" package. > > On Thursday, June 10, 2021 at 2:10:48 AM UTC+3 Mike Bayer wrote: > >> 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 /2.0 includes a very specific >> upgrade path with step-by-step instructions at >> https://docs.sqlalchemy.org/en/14/changelog/migration_20.html . >> >> >> >> On Wed, Jun 9, 2021, at 4:15 PM, Marat Sharafutdinov wrote: >> >> 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 opportunity to have 1.3 and earlier version of SQLAlchemy which is >> already in use and latest SQLAlchemy2 version to migrate gradually step by >> step, in case of Flask for example, - one API method by another. Just one >> additional way to migrate painlessly. >> >> >> -- >> SQLAlchemy - >> The Python SQL Toolkit and Object Relational Mapper >> >> http://www.sqlalchemy.org/ >> >> To post example code, please provide an MCVE: Minimal, Complete, and >> Verifiable Example. See http://stackoverflow.com/help/mcve for a full >> description. >> --- >> You received this message because you are subscribed to the Google Groups >> "sqlalchemy" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sqlalchemy+...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/sqlalchemy/730e4079-1751-4a9f-8f4a-f5fd7dde30f7n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/sqlalchemy/730e4079-1751-4a9f-8f4a-f5fd7dde30f7n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> >> -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/45d4c4e0-2241-430e-9428-3dd3ce7589ebn%40googlegroups.com.
