Open Stack

On 7/1/15, 09:03, "Mike Bayer" <mbayer at redhat.com> wrote:

>
>
>On 6/30/15 9:51 PM, Thomas Goirand wrote:
>> Hi,
>>
>> Mike nicely tried to help me to get sqla-migrate to work with sqlalchemy
>> 1.0.6 which is now in Debian. But there's some failures in Python 2.6:
>>
>> https://review.openstack.org/#/c/197144/
>>
>> Do we still care about them? Can we get them removed from -migrate? IMO,
>> supporting the last SQLA is more important than the old Py 2.6.
>
>That is very odd that there's a failure, and if this is specific to SQLA
>1.0 also then I'd be pretty worried something weird is going on.  SQLA
>still supports 2.6 only because I haven't yet had the need to really use
>2.7-isms.
>
>I'm all for making the 2.6 job non-voting here but I do want to fix this.
>
>
>
>
>>
>> Thoughts anyone?
>>
>> Cheers,
>>
>> Thomas Goirand (zigo)
>>
>> 
>>_________________________________________________________________________
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Is sqlalchemy-migrate capped on the stable branches that still support
2.6? If so, I don't see a reason against removing it. That said, this is
failing on stderr receiving output when it shouldn't. Is that a (perhaps
deprecation) warning being raised by SQLA? If so, I think that test
failure is a good thing because it's helping catch the use of something
that's deprecated in SQLA.