There was one potential incompatibility with transaction, but the zope.sqlalchemy team addressed it already ( see https://github.com/zopefoundation/zope.sqlalchemy/issues/60 ). There are deprecation warnings that are still unhandled ( see https://github.com/zopefoundation/zope.sqlalchemy/pull/64 ) but everything else should be fine.
Most of the 2.0 sqlalchemy changes are in the engine and query systems, and pretty isolated from the support the cookiecutter and zope.sqlalchemy provide. On Thursday, November 24, 2022 at 1:38:01 PM UTC-5 zsol...@gmail.com wrote: > Hi, > > I'm starting a new project from cookiecutter and I wanted to use > SQLAlchemy 2.0 (pre-release currently). > > So far I changed meta.py to > > class Base(DeclarativeBase): > metadata = my_metadata > > as well as changing the model to the new Mapped / mapped_column syntax. > > My question is that is there anything in pyramid_tm, transaction or > zope.sqlalchemy packages which needs to be changed, or this was all I > needed? > > SQLAlchemy changed a *lot* in 2.0, that's why I think the whole > transaction related part might be affected. > > If it's the case then I'll just go back to 1.4 and wait a year or so till > it matures. What do you think? > > Zsolt > > > > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/bb45eb53-c263-4d35-af74-60691ca010d5n%40googlegroups.com.
