On Mon, Feb 08, 2016 at 09:49:51PM +0100, Pjotr Prins wrote: > They will fix it when they upgrade sqlite. python-sqlalchemy is under > active development. Question is what we do for the time being with > sqlite.
I would say the culprit is python-sqlalchemy and not sqlite. So if you cannot wait for upstream to fix their package, one possibility would be to add a package for on older version of sqlite (assuming it does not present security problems) and to build python-sqlalchemy with it. It could even be a private variable only used in this input instead of a user visible variant. Andreas
