additional info using SQLAlchemy 1.1.7 or greater will show as a warning under Py2K, which hopefully Magnum should be directing into the logs, as per http://docs.sqlalchemy.org/en/latest/changelog/changelog_11.html#change-34dc3f48c4597e8b0bb377c94fd6359a.
I've confirmed Magnum is still using the legacy enginefacade, however is emitting session.begin(). Current master of magnum does not have this method so this is specific to a specific legacy version of magnum.
additional info using SQLAlchemy 1.1.7 or greater will show as a warning under Py2K, which hopefully Magnum should be directing into the logs, as per http:// docs.sqlalchemy .org/en/ latest/ changelog/ changelog_ 11.html# change- 34dc3f48c4597e8 b0bb377c94fd635 9a.
I've confirmed Magnum is still using the legacy enginefacade, however is emitting session.begin(). Current master of magnum does not have this method so this is specific to a specific legacy version of magnum.