[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] gnu: python-sqlalchemy: Update to 1.0.11 (oops: fixed name).
From: |
Pjotr Prins |
Subject: |
Re: [PATCH] gnu: python-sqlalchemy: Update to 1.0.11 (oops: fixed name). |
Date: |
Mon, 8 Feb 2016 22:09:25 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Yes, that is what I have already done. I can't afford to wait ;)
I am just wondering how many packages are broken (visibly or not).
Sqlite changed something fundamental.
Pj.
On Mon, Feb 08, 2016 at 09:57:10PM +0100, Andreas Enge wrote:
> 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
>
--