The reason this broke is because we used to load sqlalchemy as a driver, but starting with antelope we no longer support custom storage drivers and instead just instantiate the sqlalchemy code at startup. This meant that the sqlalchemy code is no longer lazy-loaded and which in turn causes that import to happen sooner in the code.
Thanks for the report and for confirming the fix.
The reason this broke is because we used to load sqlalchemy as a driver, but starting with antelope we no longer support custom storage drivers and instead just instantiate the sqlalchemy code at startup. This meant that the sqlalchemy code is no longer lazy-loaded and which in turn causes that import to happen sooner in the code.