<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 4, 2013 at 6:29 PM, Jamie Lennox <span dir="ltr"><<a href="mailto:jamielennox@redhat.com" target="_blank">jamielennox@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Adrian,<br>
<br>
The main blocker for the time being with keystoneclient and py3 is our<br>
use of a library called HTTPretty in our testing - on which there is a<br>
very recent thread. There is upstream work to make this py3 compatible<br>
but i'm not sure how quickly it's moving.<br>
<br>
Any code in keystoneclient itself that is not py33 compatible should be<br>
considered a bug - but obviously due to the missed testing we don't pick<br>
this up very often.<br>
<br>
There is no timeline at the moment, however anyone with py33 experience<br>
looking to make this happen faster could contribute to this branch on<br>
github: <a href="https://github.com/gabrielfalcao/HTTPretty/pull/124" target="_blank">https://github.com/gabrielfalcao/HTTPretty/pull/124</a> and help<br>
upstream. Once there is a py33 release available keystoneclient will not<br>
be far behind.<br>
<span class="HOEnZb"><font color="#888888"><br>
Jamie<br><br></font></span></blockquote><div><br></div><div>I have been working on getting python-keystoneclient compatible with py33, and there has some work been done. However getting httpretty py33 compatible is just the first step , there is a whole bunch of fixes that need to be done before the tests pass with py33. The differences for hmac in python-keystoneclient comes to mind.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
</font></span><div class="HOEnZb"><div class="h5"><br>
On Wed, 2013-12-04 at 20:59 +0000, Adrian Otto wrote:<br>
> Dolph,<br>
><br>
><br>
> Is anyone already focusing on py33 compatibility for<br>
> python-keystoneclient? Has that effort been scoped? I'd like to judge<br>
> whether it's reasonable to expect us to patch it up to be compatible<br>
> in the near term, or relax our expectations. For Solum, we are trying<br>
> to make all our code py33 compatible from the start, so we take it<br>
> seriously when the py33 gate fails. Please advise.<br>
><br>
><br>
> Thanks,<br>
><br>
><br>
> Adrian<br>
><br>
> On Dec 4, 2013, at 12:24 PM, Dolph Mathews <<a href="mailto:dolph.mathews@gmail.com">dolph.mathews@gmail.com</a>><br>
> wrote:<br>
><br>
> ><br>
> > On Wed, Dec 4, 2013 at 1:26 PM, Georgy Okrokvertskhov<br>
> > <<a href="mailto:gokrokvertskhov@mirantis.com">gokrokvertskhov@mirantis.com</a>> wrote:<br>
> > Hi,<br>
> ><br>
> ><br>
> > I have failed tests in gate-solum-python33 because<br>
> > kesytoneclient fails to import xmlrpclib.<br>
> > The exact error is:<br>
> > "File<br>
> > "/home/jenkins/workspace/gate-solum-python33/.tox/py33/lib/python3.3/site-packages/keystoneclient/openstack/common/jsonutils.py", line 42, in <module><br>
> > 2013-11-28 18:27:12.655 | import xmlrpclib<br>
> > 2013-11-28 18:27:12.655 | ImportError: No module named<br>
> > 'xmlrpclib<br>
> > "<br>
> > This issue appeared because of xmlrpclib was renamed in<br>
> > python33.<br>
> > Is there any plan to release a new version<br>
> > of keystoneclient with the fix for that issue? As I see it<br>
> > is fixed in master.<br>
> ><br>
> ><br>
> > If there is no new release for keystoneclient can you<br>
> > recommend any workaround for this issue?<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > I'd be happy to make a release keystoneclient, but I don't believe<br>
> > that's the only issue with python 3 at the moment (at least on the<br>
> > CLI?). For example:<br>
> ><br>
> ><br>
> > <a href="https://bugs.launchpad.net/python-keystoneclient/+bug/1249165" target="_blank">https://bugs.launchpad.net/python-keystoneclient/+bug/1249165</a><br>
> ><br>
> ><br>
> > In the current master, the above issue is only reproducible after<br>
> > syncing oslo (otherwise it fails on yet another python 3<br>
> > incompatibility).<br>
> ><br>
> ><br>
> > Thanks<br>
> > Georgy<br>
> ><br>
> > _______________________________________________<br>
> > OpenStack-dev mailing list<br>
> > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > OpenStack-dev mailing list<br>
> > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>
><br>
><br>
><br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>