Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
On 10 Dec 2013, at 09:20, Morgan Fainberg wrote: > I think the correct way to sync is to run the update.py script and submit a > review (I don’t think it’s changed recently). Seems pretty straightforward then, thanks. let see how the review goes here then : https://review.openstack.org/#/c/61042/ Cheers, Chmouel. signature.asc Description: Message signed with OpenPGP using GPGMail ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
Hi Chmouel, I think the correct way to sync is to run the update.py script and submit a review (I don’t think it’s changed recently). Cheers, Morgan On December 9, 2013 at 23:58:42, Chmouel Boudjnah (chmo...@enovance.com) wrote: On Fri, Dec 6, 2013 at 4:30 PM, Dolph Mathews wrote: ++ and the other errors I was hitting all have open patches in gerrit to see them fixed. It didn't seem like we were far off, but I haven't tested all these patches together yet to find out if they're just hiding even more problems. Either way, a py33 test run for keystoneclient will look very different very soon. It seems that gettextutils needs to be updated from oslo-incubator to get keystoneclient to py3 (minus the tests/httpprety): https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/openstack/common/gettextutils.py#L32 I would not mind doing it but I am not sure what's the process these days for syncing those modules (aside of running the update.py). Cheers, Chmouel. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
On Fri, Dec 6, 2013 at 4:30 PM, Dolph Mathews wrote: > > ++ and the other errors I was hitting all have open patches in gerrit to > see them fixed. It didn't seem like we were far off, but I haven't tested > all these patches together yet to find out if they're just hiding even more > problems. Either way, a py33 test run for keystoneclient will look very > different very soon. > It seems that gettextutils needs to be updated from oslo-incubator to get keystoneclient to py3 (minus the tests/httpprety): https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/openstack/common/gettextutils.py#L32 I would not mind doing it but I am not sure what's the process these days for syncing those modules (aside of running the update.py). Cheers, Chmouel. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
On Wed, Dec 4, 2013 at 7:48 PM, David Stanek wrote: > On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto wrote: > >> Jamie, >> >> Thanks for the guidance here. I am checking to see if any of our >> developers might take an interest in helping with the upstream work. At the >> very least, it might be nice to have some understanding of how much work >> there is to be done in HTTPretty. > > > (Dolph correct me if I am wrong, but...) > > I don't think that there is much work to be done beyond getting that pull > request merged upstream. Dolph ran the tests using the code from the pull > request somewhat successfully. The errors that we saw were just in > keystoneclient code. > > ++ and the other errors I was hitting all have open patches in gerrit to see them fixed. It didn't seem like we were far off, but I haven't tested all these patches together yet to find out if they're just hiding even more problems. Either way, a py33 test run for keystoneclient will look very different very soon. > -- > David > blog: http://www.traceback.org > twitter: http://twitter.com/dstanek > www: http://dstanek.com > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- -Dolph ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
Hi Adrian, I was going to say exactly what Jamie said (and that Jamie and Dolph had some conversations with the guy about the py3k support and the pending pull request for it). Let me know if you want/need any other voices in communicating with the guy. Cheers, Morgan On December 5, 2013 at 02:21:29, Jamie Lennox (jamielen...@redhat.com) wrote: On Thu, 2013-12-05 at 05:08 +, Adrian Otto wrote: > Hi Morgan! > > > Stackforge projects can be configured to make the CLA optional. I am > willing to speak to the HTTPretty maintainers about the benefits of > stackforge. Do we happen to know any of them? If not I can track them > down through email. > > > Adrian > The main guy's email is fairly easy to find from his github page. But I'm pretty sure he won't be interested. He's not involved in OpenStack at all. Feel free to try though. Jamie > > > -- > Adrian > > > Original message > From: Morgan Fainberg > Date:12/04/2013 6:17 PM (GMT-08:00) > To: Jamie Lennox ,"OpenStack Development Mailing List (not for usage > questions)" > Subject: Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last > released version of keystoneclient does not work with python33 > > > > On December 4, 2013 at 18:05:07, Jamie Lennox (jamielen...@redhat.com) > wrote: > > > > > On Wed, 2013-12-04 at 20:48 -0500, David Stanek wrote: > > > On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto > > > wrote: > > > Jamie, > > > > > > Thanks for the guidance here. I am checking to see if any of > > > our developers might take an interest in helping with the > > > upstream work. At the very least, it might be nice to have > > > some understanding of how much work there is to be done in > > > HTTPretty. > > > > > > > > > (Dolph correct me if I am wrong, but...) > > > > > > > > > I don't think that there is much work to be done beyond getting > > that > > > pull request merged upstream. Dolph ran the tests using the code > > from > > > the pull request somewhat successfully. The errors that we saw > > were > > > just in keystoneclient code. > > > > But I don't think that there own test suite runs under py33 with > > that > > branch. So they've hit the main issues, but we won't get a release > > in > > that state. > Should we offer to bring HTTPretty under something like stackforge and > leverage our CI infrastructure? Not sure how open the > owner/maintainers would be to this, but it would help to solve that > issue… downside is that pull-requests are no longer (gerrit instead) > used and IIRC CLA is still required for stackforge projects (might be > a detractor). Just a passing thought (that might be irrelevant > depending on the owner/maintainer’s point of view). > > > > > —Morgan > > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
On Thu, 2013-12-05 at 05:08 +, Adrian Otto wrote: > Hi Morgan! > > > Stackforge projects can be configured to make the CLA optional. I am > willing to speak to the HTTPretty maintainers about the benefits of > stackforge. Do we happen to know any of them? If not I can track them > down through email. > > > Adrian > The main guy's email is fairly easy to find from his github page. But I'm pretty sure he won't be interested. He's not involved in OpenStack at all. Feel free to try though. Jamie > > > -- > Adrian > > > Original message > From: Morgan Fainberg > Date:12/04/2013 6:17 PM (GMT-08:00) > To: Jamie Lennox ,"OpenStack Development Mailing List (not for usage > questions)" > Subject: Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last > released version of keystoneclient does not work with python33 > > > > On December 4, 2013 at 18:05:07, Jamie Lennox (jamielen...@redhat.com) > wrote: > > > > > On Wed, 2013-12-04 at 20:48 -0500, David Stanek wrote: > > > On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto > > > wrote: > > > Jamie, > > > > > > Thanks for the guidance here. I am checking to see if any of > > > our developers might take an interest in helping with the > > > upstream work. At the very least, it might be nice to have > > > some understanding of how much work there is to be done in > > > HTTPretty. > > > > > > > > > (Dolph correct me if I am wrong, but...) > > > > > > > > > I don't think that there is much work to be done beyond getting > > that > > > pull request merged upstream. Dolph ran the tests using the code > > from > > > the pull request somewhat successfully. The errors that we saw > > were > > > just in keystoneclient code. > > > > But I don't think that there own test suite runs under py33 with > > that > > branch. So they've hit the main issues, but we won't get a release > > in > > that state. > Should we offer to bring HTTPretty under something like stackforge and > leverage our CI infrastructure? Not sure how open the > owner/maintainers would be to this, but it would help to solve that > issue… downside is that pull-requests are no longer (gerrit instead) > used and IIRC CLA is still required for stackforge projects (might be > a detractor). Just a passing thought (that might be irrelevant > depending on the owner/maintainer’s point of view). > > > > > —Morgan > > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
Hi Morgan! Stackforge projects can be configured to make the CLA optional. I am willing to speak to the HTTPretty maintainers about the benefits of stackforge. Do we happen to know any of them? If not I can track them down through email. Adrian -- Adrian Original message From: Morgan Fainberg Date:12/04/2013 6:17 PM (GMT-08:00) To: Jamie Lennox ,"OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33 On December 4, 2013 at 18:05:07, Jamie Lennox (jamielen...@redhat.com<mailto://jamielen...@redhat.com>) wrote: On Wed, 2013-12-04 at 20:48 -0500, David Stanek wrote: > On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto > wrote: > Jamie, > > Thanks for the guidance here. I am checking to see if any of > our developers might take an interest in helping with the > upstream work. At the very least, it might be nice to have > some understanding of how much work there is to be done in > HTTPretty. > > > (Dolph correct me if I am wrong, but...) > > > I don't think that there is much work to be done beyond getting that > pull request merged upstream. Dolph ran the tests using the code from > the pull request somewhat successfully. The errors that we saw were > just in keystoneclient code. But I don't think that there own test suite runs under py33 with that branch. So they've hit the main issues, but we won't get a release in that state. Should we offer to bring HTTPretty under something like stackforge and leverage our CI infrastructure? Not sure how open the owner/maintainers would be to this, but it would help to solve that issue… downside is that pull-requests are no longer (gerrit instead) used and IIRC CLA is still required for stackforge projects (might be a detractor). Just a passing thought (that might be irrelevant depending on the owner/maintainer’s point of view). —Morgan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
Excerpts from Adrian Otto's message of 2013-12-04 16:53:16 -0800: > Clint, > > On Dec 4, 2013, at 4:06 PM, Clint Byrum > wrote: > > > Excerpts from Adrian Otto's message of 2013-12-04 15:44:45 -0800: > >> Jamie, > >> > >> Thanks for the guidance here. I am checking to see if any of our > >> developers might take an interest in helping with the upstream work. At > >> the very least, it might be nice to have some understanding of how much > >> work there is to be done in HTTPretty. > >> > > > > Seems to me that we're still too early in the process for a downstream > > application like Solum to gate on py3k. It will be more productive to > > focus efforts on getting upstreams in-line and making sure they stay > > in-line. > > The py33 work is going to need to get done at some point. If we are py33 > compatible from the start, there is less work to do later. I am suggesting > that we clean up the upstreams. Keystone, and by association HTTPretty are > Solum's upstreams for our auth feature. That's where I am suggesting we take > a look. I totally agree, if you can do it now, fantastic. But you already depend on python-keystoneclient, which has not done it yet. And they cannot do it because HTTPretty has not done it. So upstream is where the effort must happen at the moment. Don't get me wrong, downstream applications like Solum are the driving force behind the upstream library work. Solum should be pushing, always, for py33 compliance. However, gating on it at this point would be ill advised. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
On December 4, 2013 at 18:05:07, Jamie Lennox (jamielen...@redhat.com) wrote: On Wed, 2013-12-04 at 20:48 -0500, David Stanek wrote: > On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto > wrote: > Jamie, > > Thanks for the guidance here. I am checking to see if any of > our developers might take an interest in helping with the > upstream work. At the very least, it might be nice to have > some understanding of how much work there is to be done in > HTTPretty. > > > (Dolph correct me if I am wrong, but...) > > > I don't think that there is much work to be done beyond getting that > pull request merged upstream. Dolph ran the tests using the code from > the pull request somewhat successfully. The errors that we saw were > just in keystoneclient code. But I don't think that there own test suite runs under py33 with that branch. So they've hit the main issues, but we won't get a release in that state. Should we offer to bring HTTPretty under something like stackforge and leverage our CI infrastructure? Not sure how open the owner/maintainers would be to this, but it would help to solve that issue… downside is that pull-requests are no longer (gerrit instead) used and IIRC CLA is still required for stackforge projects (might be a detractor). Just a passing thought (that might be irrelevant depending on the owner/maintainer’s point of view). —Morgan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
On Wed, 2013-12-04 at 20:48 -0500, David Stanek wrote: > On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto > wrote: > Jamie, > > Thanks for the guidance here. I am checking to see if any of > our developers might take an interest in helping with the > upstream work. At the very least, it might be nice to have > some understanding of how much work there is to be done in > HTTPretty. > > > (Dolph correct me if I am wrong, but...) > > > I don't think that there is much work to be done beyond getting that > pull request merged upstream. Dolph ran the tests using the code from > the pull request somewhat successfully. The errors that we saw were > just in keystoneclient code. But I don't think that there own test suite runs under py33 with that branch. So they've hit the main issues, but we won't get a release in that state. > -- > David > blog: http://www.traceback.org > twitter: http://twitter.com/dstanek > www: http://dstanek.com > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto wrote: > Jamie, > > Thanks for the guidance here. I am checking to see if any of our > developers might take an interest in helping with the upstream work. At the > very least, it might be nice to have some understanding of how much work > there is to be done in HTTPretty. (Dolph correct me if I am wrong, but...) I don't think that there is much work to be done beyond getting that pull request merged upstream. Dolph ran the tests using the code from the pull request somewhat successfully. The errors that we saw were just in keystoneclient code. -- David blog: http://www.traceback.org twitter: http://twitter.com/dstanek www: http://dstanek.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
Adrian, I had a look a little while ago and I don't *think* it's too bad. Because it's hooking into sockets and dealing with web requests though there is a lot of messing with what is unicode vs ascii and the py2 vs py3 differences. I'm sure it's doable, but i hate those kind of problems :) >From a dev point of view it's a good library and i recommend the various clients look at it rather than our home grown client stubbing. Internally he's done some interesting things like maintaining his own compat rather than just using six, and it's tested using an unknown framework that does a hook into PyObject * (CPython) which is just wrong. But we don't need to fix the whole project, just py33. Jamie On Wed, 2013-12-04 at 23:44 +, Adrian Otto wrote: > Jamie, > > Thanks for the guidance here. I am checking to see if any of our developers > might take an interest in helping with the upstream work. At the very least, > it might be nice to have some understanding of how much work there is to be > done in HTTPretty. > > Cheers, > > Adrian > > On Dec 4, 2013, at 3:29 PM, Jamie Lennox > wrote: > > > Adrian, > > > > The main blocker for the time being with keystoneclient and py3 is our > > use of a library called HTTPretty in our testing - on which there is a > > very recent thread. There is upstream work to make this py3 compatible > > but i'm not sure how quickly it's moving. > > > > Any code in keystoneclient itself that is not py33 compatible should be > > considered a bug - but obviously due to the missed testing we don't pick > > this up very often. > > > > There is no timeline at the moment, however anyone with py33 experience > > looking to make this happen faster could contribute to this branch on > > github: https://github.com/gabrielfalcao/HTTPretty/pull/124 and help > > upstream. Once there is a py33 release available keystoneclient will not > > be far behind. > > > > Jamie > > > > On Wed, 2013-12-04 at 20:59 +, Adrian Otto wrote: > >> Dolph, > >> > >> > >> Is anyone already focusing on py33 compatibility for > >> python-keystoneclient? Has that effort been scoped? I'd like to judge > >> whether it's reasonable to expect us to patch it up to be compatible > >> in the near term, or relax our expectations. For Solum, we are trying > >> to make all our code py33 compatible from the start, so we take it > >> seriously when the py33 gate fails. Please advise. > >> > >> > >> Thanks, > >> > >> > >> Adrian > >> > >> On Dec 4, 2013, at 12:24 PM, Dolph Mathews > >> wrote: > >> > >>> > >>> On Wed, Dec 4, 2013 at 1:26 PM, Georgy Okrokvertskhov > >>> wrote: > >>>Hi, > >>> > >>> > >>>I have failed tests in gate-solum-python33 because > >>>kesytoneclient fails to import xmlrpclib. > >>>The exact error is: > >>>"File > >>> > >>> "/home/jenkins/workspace/gate-solum-python33/.tox/py33/lib/python3.3/site-packages/keystoneclient/openstack/common/jsonutils.py", > >>> line 42, in > >>>2013-11-28 18:27:12.655 | import xmlrpclib > >>>2013-11-28 18:27:12.655 | ImportError: No module named > >>>'xmlrpclib > >>>" > >>>This issue appeared because of xmlrpclib was renamed in > >>>python33. > >>>Is there any plan to release a new version > >>>of keystoneclient with the fix for that issue? As I see it > >>>is fixed in master. > >>> > >>> > >>>If there is no new release for keystoneclient can you > >>>recommend any workaround for this issue? > >>> > >>> > >>> > >>> > >>> I'd be happy to make a release keystoneclient, but I don't believe > >>> that's the only issue with python 3 at the moment (at least on the > >>> CLI?). For example: > >>> > >>> > >>> https://bugs.launchpad.net/python-keystoneclient/+bug/1249165 > >>> > >>> > >>> In the current master, the above issue is only reproducible after > >>> syncing oslo (otherwise it fails on yet another python 3 > >>> incompatibility). > >>> > >>> > >>>Thanks > >>>Georgy > >>> > >>>___ > >>>OpenStack-dev mailing list > >>>OpenStack-dev@lists.openstack.org > >>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >>> > >>> > >>> > >>> > >>> > >>> ___ > >>> OpenStack-dev mailing list > >>> OpenStack-dev@lists.openstack.org > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > >> > >> > > > > > > ___ > > OpenStack-dev mailing list > > OpenStack-dev@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
Clint, On Dec 4, 2013, at 4:06 PM, Clint Byrum wrote: > Excerpts from Adrian Otto's message of 2013-12-04 15:44:45 -0800: >> Jamie, >> >> Thanks for the guidance here. I am checking to see if any of our developers >> might take an interest in helping with the upstream work. At the very least, >> it might be nice to have some understanding of how much work there is to be >> done in HTTPretty. >> > > Seems to me that we're still too early in the process for a downstream > application like Solum to gate on py3k. It will be more productive to > focus efforts on getting upstreams in-line and making sure they stay > in-line. The py33 work is going to need to get done at some point. If we are py33 compatible from the start, there is less work to do later. I am suggesting that we clean up the upstreams. Keystone, and by association HTTPretty are Solum's upstreams for our auth feature. That's where I am suggesting we take a look. Adrian ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
Excerpts from Adrian Otto's message of 2013-12-04 15:44:45 -0800: > Jamie, > > Thanks for the guidance here. I am checking to see if any of our developers > might take an interest in helping with the upstream work. At the very least, > it might be nice to have some understanding of how much work there is to be > done in HTTPretty. > Seems to me that we're still too early in the process for a downstream application like Solum to gate on py3k. It will be more productive to focus efforts on getting upstreams in-line and making sure they stay in-line. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33
Jamie, Thanks for the guidance here. I am checking to see if any of our developers might take an interest in helping with the upstream work. At the very least, it might be nice to have some understanding of how much work there is to be done in HTTPretty. Cheers, Adrian On Dec 4, 2013, at 3:29 PM, Jamie Lennox wrote: > Adrian, > > The main blocker for the time being with keystoneclient and py3 is our > use of a library called HTTPretty in our testing - on which there is a > very recent thread. There is upstream work to make this py3 compatible > but i'm not sure how quickly it's moving. > > Any code in keystoneclient itself that is not py33 compatible should be > considered a bug - but obviously due to the missed testing we don't pick > this up very often. > > There is no timeline at the moment, however anyone with py33 experience > looking to make this happen faster could contribute to this branch on > github: https://github.com/gabrielfalcao/HTTPretty/pull/124 and help > upstream. Once there is a py33 release available keystoneclient will not > be far behind. > > Jamie > > On Wed, 2013-12-04 at 20:59 +, Adrian Otto wrote: >> Dolph, >> >> >> Is anyone already focusing on py33 compatibility for >> python-keystoneclient? Has that effort been scoped? I'd like to judge >> whether it's reasonable to expect us to patch it up to be compatible >> in the near term, or relax our expectations. For Solum, we are trying >> to make all our code py33 compatible from the start, so we take it >> seriously when the py33 gate fails. Please advise. >> >> >> Thanks, >> >> >> Adrian >> >> On Dec 4, 2013, at 12:24 PM, Dolph Mathews >> wrote: >> >>> >>> On Wed, Dec 4, 2013 at 1:26 PM, Georgy Okrokvertskhov >>> wrote: >>>Hi, >>> >>> >>>I have failed tests in gate-solum-python33 because >>>kesytoneclient fails to import xmlrpclib. >>>The exact error is: >>>"File >>> >>> "/home/jenkins/workspace/gate-solum-python33/.tox/py33/lib/python3.3/site-packages/keystoneclient/openstack/common/jsonutils.py", >>> line 42, in >>>2013-11-28 18:27:12.655 | import xmlrpclib >>>2013-11-28 18:27:12.655 | ImportError: No module named >>>'xmlrpclib >>>" >>>This issue appeared because of xmlrpclib was renamed in >>>python33. >>>Is there any plan to release a new version >>>of keystoneclient with the fix for that issue? As I see it >>>is fixed in master. >>> >>> >>>If there is no new release for keystoneclient can you >>>recommend any workaround for this issue? >>> >>> >>> >>> >>> I'd be happy to make a release keystoneclient, but I don't believe >>> that's the only issue with python 3 at the moment (at least on the >>> CLI?). For example: >>> >>> >>> https://bugs.launchpad.net/python-keystoneclient/+bug/1249165 >>> >>> >>> In the current master, the above issue is only reproducible after >>> syncing oslo (otherwise it fails on yet another python 3 >>> incompatibility). >>> >>> >>>Thanks >>>Georgy >>> >>>___ >>>OpenStack-dev mailing list >>>OpenStack-dev@lists.openstack.org >>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> >>> >>> >>> ___ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
