<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Hi Étienne -<br></div><div><br></div><div>SQLSoup's repository is currently at <a href="https://github.com/zzzeek/sqlsoup">https://github.com/zzzeek/sqlsoup</a> <br></div><div><br></div><div>However it has not been maintained for many years and would not be expected to work with modern versions of SQLAlchemy. Feel free to remove it from your distributions.<br></div><div><br></div><div>- mike<br></div><div><br></div><div><br></div><div><br></div><div>On Fri, Oct 8, 2021, at 4:22 PM, Étienne Mollier wrote:<br></div><blockquote type="cite" id="qt" style=""><div>Hi Michael,<br></div><div><br></div><div>Sorry to contact you like this, but since the forge disappeared<br></div><div>from bitbucket, we were keeping track of the pypi repository<br></div><div>instead, but it hasn't much moved since 2016 [0], and we don't<br></div><div>know where else to pull upgrades, report issues, etc. Per<br></div><div>chance, do you still happen to work on sqlsoup on some public<br></div><div>location?<br></div><div><br></div><div>[0]: <a href="https://pypi.org/project/sqlsoup/">https://pypi.org/project/sqlsoup/</a><br></div><div><br></div><div>There is an impending upgrade of SQLAlchemy from version 1.3 to<br></div><div>1.4 in Debian Testing, but there are a couple of issues which<br></div><div>hold the process in Unstable. One of them is that it introduces<br></div><div>regressions in our current version of sqlsoup, per Thomas' bug<br></div><div>report [1].<br></div><div><br></div><div>[1]: <a href="http://bugs.debian.org/995781">http://bugs.debian.org/995781</a><br></div><div><br></div><div>Excerpt from the migration test log [2], which basically consist<br></div><div>in running `python3 -c "import sqlsoup; print(sqlsoup)"`:<br></div><div><br></div><div>Testing with python3.9:<br></div><div>Traceback (most recent call last):<br></div><div> File "<string>", line 1, in <module><br></div><div> File "/usr/lib/python3/dist-packages/sqlsoup.py", line 11, in <module><br></div><div> from sqlalchemy.orm.interfaces import MapperExtension, EXT_CONTINUE<br></div><div>ImportError: cannot import name 'MapperExtension' from 'sqlalchemy.orm.interfaces' (/usr/lib/python3/dist-packages/sqlalchemy/orm/interfaces.py)<br></div><div><br></div><div>[2]: <a href="https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-sqlsoup/15788076/log.gz">https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-sqlsoup/15788076/log.gz</a><br></div><div><br></div><div>I begun to have a peek at the issue and rapidly found changelogs<br></div><div>for SQLAchemy [3], but once the first symptom is worked around,<br></div><div>I begin pull more hairy issues with relation to functions which<br></div><div>were apparently not documented on sqlalchemy side, while running<br></div><div>the unit test suite:<br></div><div><br></div><div>======================================================================<br></div><div>ERROR: test_bad_names (tests.test_sqlsoup.SQLSoupTest)<br></div><div>----------------------------------------------------------------------<br></div><div>Traceback (most recent call last):<br></div><div> File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_sqlsoup/build/tests/test_sqlsoup.py", line 105, in tes<br></div><div>t_bad_names<br></div><div> str(db.bad_names.c.query)<br></div><div> File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_sqlsoup/build/sqlsoup.py", line 463, in __getattr__<br></div><div> return self.entity(attr)<br></div><div> File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_sqlsoup/build/sqlsoup.py", line 460, in entity<br></div><div> return self.map_to(attr, tablename=attr, schema=schema)<br></div><div> File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_sqlsoup/build/sqlsoup.py", line 366, in map_to<br></div><div> mapped_cls = _class_for_table(<br></div><div> File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_sqlsoup/build/sqlsoup.py", line 133, in _class_for_table<br></div><div> selectable = expression._clause_element_as_expr(selectable)<br></div><div>AttributeError: module 'sqlalchemy.sql.expression' has no attribute '_clause_element_as_expr'<br></div><div><br></div><div>[3]: <a href="https://docs.sqlalchemy.org/en/14/changelog/changelog_14.html#change-6daf2f59ac2438ef9c8213e9ebeac157">https://docs.sqlalchemy.org/en/14/changelog/changelog_14.html#change-6daf2f59ac2438ef9c8213e9ebeac157</a><br></div><div><br></div><div>(I wrote a patch, in attachment, to get there, but I am not too<br></div><div>happy about it, feels like just a crude workaround to hide the<br></div><div>first symptom.)<br></div><div><br></div><div>Please let us know if you have time to investigate this,<br></div><div>otherwise the sqlsoup package is at risk of being removed from<br></div><div>Debian Testing to avoid blocking further the SQLAlchemy upgrade.<br></div><div><br></div><div>Kind Regards,<br></div><div>-- <br></div><div>Étienne Mollier <<a href="mailto:emollier@emlwks999.eu">emollier@emlwks999.eu</a>><br></div><div>Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da<br></div><div>Sent from /dev/pts/2, please excuse my verbosity.<br></div><div><br></div><div><br></div><div><b>Attachments:</b><br></div><ul><li>migrate-to-mapper-events.patch<br></li><li>signature.asc<br></li></ul></blockquote><div><br></div></body></html>