Thanks to Herculean work of Ilya - and with a little bit of my help we now have SQLALchemy 2 tests running in our "canary builds" now.
Currently (until FAB 5) they only run in "canary" builds and only in Python 3,13 (because that's where we have no FAB) but it will allow us to see if we do not add anything "not working" for sqlalchemy 2. That was a bit of a difficult one - because SQLA2 hanged with MySQL for our migrations, in a strange way that did not allow us to easily inspect the problem - we've worked together with Ilya and I added wya better diagnostics for this case - yet eventually Ilya solved it by adding autocommit while running the migration - which seemed to help :). More to come soon when we get to FAB 5 upgrade - we might be able to migrate to sqlalchemy 2 for 3.1 (keep fingers crossed). FAB 5 alpha 9 has been recently released by daniel and we are about to take it for a spin. J.