Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

2015-06-11 Thread Thomas Goirand
On 06/12/2015 12:34 AM, Thomas Goirand wrote: On 06/10/2015 11:23 PM, Mike Bayer wrote: On 6/10/15 5:18 PM, Thomas Goirand wrote: On 06/10/2015 04:52 PM, Mike Bayer wrote: whew! :) Do you know why it fails with Kilo? https://review.openstack.org/#/c/190062/ I noticed this, I don't know

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

2015-06-11 Thread Thomas Goirand
On 06/10/2015 11:23 PM, Mike Bayer wrote: On 6/10/15 5:18 PM, Thomas Goirand wrote: On 06/10/2015 04:52 PM, Mike Bayer wrote: whew! :) Do you know why it fails with Kilo? https://review.openstack.org/#/c/190062/ I noticed this, I don't know very well how the requirements get

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

2015-06-10 Thread Thomas Goirand
Hi Mike, Thanks a lot for your quick reply which is very useful to me. On 06/09/2015 07:08 PM, Mike Bayer wrote: On 6/9/15 9:26 AM, Thomas Goirand wrote: Hi, The python-sqlalchemy package has been uploaded to Debian Experimental, and is about to be uploaded to Debian Unstable. So I wonder

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

2015-06-10 Thread Mike Bayer
On 6/10/15 3:26 AM, Thomas Goirand wrote: Hi Mike, Thanks a lot for your quick reply which is very useful to me. On 06/09/2015 07:08 PM, Mike Bayer wrote: On 6/9/15 9:26 AM, Thomas Goirand wrote: Hi, The python-sqlalchemy package has been uploaded to Debian Experimental, and is about to

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

2015-06-10 Thread Mike Bayer
On 6/10/15 5:18 PM, Thomas Goirand wrote: On 06/10/2015 04:52 PM, Mike Bayer wrote: whew! :) Do you know why it fails with Kilo? https://review.openstack.org/#/c/190062/ I noticed this, I don't know very well how the requirements get distributed around but seems like it is not happening

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

2015-06-10 Thread Thomas Goirand
On 06/10/2015 04:52 PM, Mike Bayer wrote: On 6/10/15 3:26 AM, Thomas Goirand wrote: Hi Mike, Thanks a lot for your quick reply which is very useful to me. On 06/09/2015 07:08 PM, Mike Bayer wrote: On 6/9/15 9:26 AM, Thomas Goirand wrote: Hi, The python-sqlalchemy package has been

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

2015-06-10 Thread Ian Cordasco
I think it would first require a version of oslo.db to be released inside stable/kilo's bounds that uncapped SQLAlchemy first since the requirement in the version of oslo.db installed is what you see here http://logs.openstack.org/62/190062/2/check/check-tempest-dsvm-neutron-full

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

2015-06-09 Thread Mike Bayer
On 6/9/15 9:26 AM, Thomas Goirand wrote: Hi, The python-sqlalchemy package has been uploaded to Debian Experimental, and is about to be uploaded to Debian Unstable. So I wonder what's the state of the project regarding upgrading SQLA. Maybe Mike can tell what kind of issue we may run into?

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

2015-06-09 Thread Mike Bayer
On 6/9/15 1:08 PM, Mike Bayer wrote: So for Openstack, we would mostly worry about code that is doing things oddly in some unexpected way, however all the Openstack code I've seen tends to be very ORM centric and uses the ORM very conservatively so I don't anticipate any problems. I

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

2015-06-09 Thread Joe Gordon
On Tue, Jun 9, 2015 at 8:08 PM, Mike Bayer mba...@redhat.com wrote: On 6/9/15 9:26 AM, Thomas Goirand wrote: Hi, The python-sqlalchemy package has been uploaded to Debian Experimental, and is about to be uploaded to Debian Unstable. So I wonder what's the state of the project regarding

[openstack-dev] [all] Switching to SQLAlchemy 1.0.x

2015-06-09 Thread Thomas Goirand
Hi, The python-sqlalchemy package has been uploaded to Debian Experimental, and is about to be uploaded to Debian Unstable. So I wonder what's the state of the project regarding upgrading SQLA. Maybe Mike can tell what kind of issue we may run into? How much work will it be to switch to SQLA