<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 21, 2015 at 1:37 PM, Ian Cordasco <span dir="ltr"><<a href="mailto:ian.cordasco@rackspace.com" target="_blank">ian.cordasco@rackspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5">On 4/16/15, 17:54, "Clint Byrum" <<a href="mailto:clint@fewbar.com">clint@fewbar.com</a>> wrote:<br>
<br>
>Excerpts from Joe Gordon's message of 2015-04-16 15:15:01 -0700:<br>
>> On Fri, Apr 10, 2015 at 4:01 AM, Victor Stinner <<a href="mailto:vstinner@redhat.com">vstinner@redhat.com</a>><br>
>>wrote:<br>
>><br>
>> > > <a href="https://wiki.openstack.org/wiki/Python3#Dependencies" target="_blank">https://wiki.openstack.org/wiki/Python3#Dependencies</a> appears to be<br>
>> > fairly out of date.<br>
>> ><br>
>> > You're right. I updated this wiki page. In practice, much more<br>
>>OpenStack<br>
>> > clients, Common Libraries and Development Tools are already Python 3<br>
>> > compatible. I added the link to my pull request for Oslo Messaging.<br>
>> ><br>
>> > > It would be nice to get a better sense of what the remaining<br>
>>libraries<br>
>> > to port over are before the summit so we can start planning how to do<br>
>>the<br>
>> > python34 migration.<br>
>> ><br>
>> > I checked quickly. There are small libraries like pyEClib required by<br>
>> > Swift, but the major blocker libraries are: MySQL-Python, suds,<br>
>>Paste. For<br>
>> > oslo.db, it's already Python 3 compatible no?<br>
>> ><br>
>> ><br>
>> > * MySQL-Python<br>
>> ><br>
>> > MySQL-Python doesn't look to be active (last commit in january 2014).<br>
>> > There are multiple Python 3 pending pull requests:<br>
>> > <a href="https://github.com/farcepest/MySQLdb1/pulls" target="_blank">https://github.com/farcepest/MySQLdb1/pulls</a><br>
>> ><br>
>> > Mike Bayer is evaluating PyMySQL which is Python 3 compatible:<br>
>> > <a href="https://wiki.openstack.org/wiki/PyMySQL_evaluation" target="_blank">https://wiki.openstack.org/wiki/PyMySQL_evaluation</a><br>
>> ><br>
>> > See also <a href="https://github.com/farcepest/moist" target="_blank">https://github.com/farcepest/moist</a> (is it alive? is it<br>
>>Python 3<br>
>> > compatible?)<br>
>> ><br>
>> ><br>
>> > * suds<br>
>> ><br>
>> > There is <a href="https://bitbucket.org/jurko/suds" target="_blank">https://bitbucket.org/jurko/suds</a> : a fork compatible with<br>
>>Python<br>
>> > 3. Global requirements contain this comment:<br>
>> ><br>
>> > # NOTE(dims): suds is not python 3.x compatible, suds-jurko is a fork<br>
>>that<br>
>> > # works with py3x. oslo.vmware would convert to suds-jurko first then<br>
>>nova<br>
>> > # and cinder would follow. suds should be remove immediately once<br>
>>those<br>
>> > # projects move to suds-jurko for all jobs.<br>
>> ><br>
>> ><br>
>> > * Paste<br>
>> ><br>
>> > I already fixed Python 3 compatibility issues and my changes were<br>
>>merged,<br>
>> > but there is no release including my fixes yet :-(<br>
>> ><br>
>> > I heard that Paste is completly outdated and should be replaced. Ok,<br>
>>but<br>
>> > in practice it's still used and not Python 3 compatible.<br>
>> ><br>
>> > Workaround: use the development (git) version of Paste.<br>
>> ><br>
>> ><br>
>> > For the full list, see the wiki page:<br>
>> > <a href="https://wiki.openstack.org/wiki/Python3#Core_OpenStack_projects" target="_blank">https://wiki.openstack.org/wiki/Python3#Core_OpenStack_projects</a><br>
>><br>
>><br>
>> Thanks for updating the wiki page that is a very useful list.<br>
>><br>
>> From the looks of things, it seems like nova getting Python3 support in<br>
>> Liberty is not going to happen. But we can make good progress in<br>
>> dependencies sorted out. By fixing the dependencies and switching a few<br>
>>out<br>
>> for better ones.<br>
>><br>
>> What are your thoughts on how to tackle sqlalchemy-migrate? It looks<br>
>>like<br>
>> that is a blocker for several projects. And something I think we have<br>
>> wanted to move off of for some time now.<br>
>><br>
><br>
>IMHO it is quite a bit easier to port something to python 3 than to<br>
>move off of it entirely. I'd say it's worth it for forward progress to<br>
>try and port sqlalchemy-migrate, even if that means the effort becomes<br>
>a sunk cost in a year.<br>
<br>
</div></div>Also, isn’t sqlalchemy-migrate something we currently maintain (or a group<br>
of OpenStack developers do it for OpenStack. Can’t we work with them to<br>
add support for Python 3?<br></blockquote><div><br></div><div>yup <a href="https://github.com/stackforge/sqlalchemy-migrate">https://github.com/stackforge/sqlalchemy-migrate</a>. The better question is: 'is it worth adding support in versus moving over to alembic, since we want to do that anyway?' I don't personally have an answer for that.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=""><div class="h5"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>