[openstack-dev] sqlalchemy version regression

Pádraig Brady P at draigBrady.com
Mon Sep 23 11:15:14 UTC 2013


On 09/23/2013 06:48 AM, Thomas Goirand wrote:
> On 09/23/2013 01:36 PM, Thomas Goirand wrote:
>> On 09/23/2013 11:04 AM, Pádraig Brady wrote:
>>> OpenStack should be compatible with sqlalchemy 0.8.x at this stage,
>>> or should be easily tweaked to be so.
>>
>> My view as well.
>>
>>> sqlalchemy-migrate will be a bit awkward though as upstream
>>> seems to have moved to alembic and is no longer that interested in maintenance/releases.
>>> So what would be the best way to handle that?
>>
>> This has already been discussed in July:
>> http://lists.openstack.org/pipermail/openstack-dev/2013-July/011755.html
>>
>> However, I'm not sure how the plan went through.
>>
>>> For distros it's easy, just patch their latest python-migrate-0.7.2 packages with:
>>> http://pkgs.fedoraproject.org/cgit/python-migrate.git/plain/python-migrate-sqlalchemy-0.8.patch
>>> and maybe this for postgres support too:
>>> http://www.mergely.com/editor?lhs=https://raw.github.com/lugensa/sqlalchemy-migrate/1f87b7c4/migrate/changeset/ansisql.py&rhs=https://raw.github.com/lugensa/sqlalchemy-migrate/master/migrate/changeset/ansisql.py
>>
>> Is this the new upstream repository?
>>
>> I have already applied some patches to fix sqlalchemy-migrate wrt
>> sqlalchemy 0.8 in Debian. I believe that was enough to make it work.
>>
>> Thomas
> 
> Having a deeper look, I have found:
> https://github.com/stackforge/sqlalchemy-migrate

Cool, and both the above patches are already there.
The first with:
  https://github.com/stackforge/sqlalchemy-migrate/commit/2ff11c17
  https://github.com/stackforge/sqlalchemy-migrate/commit/74ccf7a3
The second (which I have an untested alternative for) at:
  https://github.com/stackforge/sqlalchemy-migrate/commit/c670d1d3#commitcomment-4154121

> However, there's no new release. Could someone tag and release a new version

I suppose we might tag/use a version between 0.7.2 >= and <= 0.7.3
to allow official upstream to release in future without clashes?
Or do we use 0.8... to indicate sqlalchemy 0.8 compat?

Oh I see we've pypi creds for this too:
http://lists.openstack.org/pipermail/openstack-dev/2013-July/011767.html
So we can control versions from now on?

> so that it can be packaged in Debian?

I'd update Fedora/EPEL to use that release if available too.

thanks!
Pádraig.



More information about the OpenStack-dev mailing list