Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
I have updated it. Thank you for sharing a link. On Mon, Jul 27, 2015 at 3:44 PM, Victor Stinner vstin...@redhat.com wrote: Hi, On 27/07/2015 12:35, Roman Vasilets wrote: Hi, just what to share with you. Rally project also have voting py34 jobs. Thank you. Cool! I don't know if Rally port the Python 3 is complete or not, so I wrote work in progress. Please update the wiki page if the port is done: https://wiki.openstack.org/wiki/Python3#OpenStack_applications Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
Hi, On 27/07/2015 12:35, Roman Vasilets wrote: Hi, just what to share with you. Rally project also have voting py34 jobs. Thank you. Cool! I don't know if Rally port the Python 3 is complete or not, so I wrote work in progress. Please update the wiki page if the port is done: https://wiki.openstack.org/wiki/Python3#OpenStack_applications Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
Thomas, 1.56 of python-memcached with haypo's fix was released yesterday. -- dims On Mon, Jul 27, 2015 at 4:53 AM, Thomas Goirand z...@debian.org wrote: On 07/20/2015 08:26 PM, Brant Knudson wrote: On Fri, Jul 17, 2015 at 7:32 AM, Victor Stinner vstin...@redhat.com mailto:vstin...@redhat.com wrote: Hi, ... (3) keystonemiddleware: blocked by python-memcached, I sent a pull request 3 months ago and I'm still waiting... https://github.com/linsomniac/python-memcached/pull/67 I may fork the project if the maintainer never reply. Read the current thread [all] Non-responsive upstream libraries (python34 specifically) on openstack-dev. ... Victor keystonemiddleware has had a py34 gate for a long time. The tests run without python-memcache installed since the tests are skipped if memcache isn't available. We've got a separate test-requirements-py34.txt that doesn't include python-memcache. This has been causing problems lately since the requirements job now fails since there are duplicate requirements in multiple files (test-requirements-py34 is just test-requirements with python-memcache removed). Well, we should IMO either get rid of python-memcache completely (in the favor of pymemcache), or worse case fork it, since Victor opened a pull request to fix it MONTHS ago. I proposed a change to global-requirements to mark python-memcache as not working on py34: https://review.openstack.org/#/c/203437/ and then we'll have to change keystonemiddleware to merge the test-requirements-py34 into test-requirements: https://review.openstack.org/#/c/197254/ . Hiding the issue will not make it go away. Thomas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
Hi, just what to share with you. Rally project also have voting py34 jobs. Thank you. On Fri, Jul 17, 2015 at 2:32 PM, Victor Stinner vstin...@redhat.com wrote: Hi, We are close to having a voting py34 gate on all OpenStack libraries and applications. I just made the py34 gate voting for the 5 following projects: * keystone * heat * glance_store: Glance library (py34 is already voting in Glance) * os-brick: Cinder library (py34 is already voting in Cinder) * sqlalchemy-migrate A voting py34 gate means that we cannot reintroduce Python 3 regressions in the code tested by tox -e py34. Currently, only a small subset of test suites is executed on Python 3.4, but the subset is growing constantly and it already helps to detect various kinds of Python 3 issues. Sirushti Murugesan (who is porting Heat to Python 3) and me proposed a talk Python 3 is coming! to the next OpenStack Summit at Tokyo. We will explain the plan to port OpenStack to Python in depth. There are only 4 remaining projects without py34 voting gate: (1) swift: I sent patches, see the Fix tox -e py34 patch: https://review.openstack.org/#/q/project:openstack/swift+branch:master+topic:py3,n,z (2) horizon: I sent patches: https://review.openstack.org/#/q/topic:bp/porting-python3+project:openstack/horizon,n,z (3) keystonemiddleware: blocked by python-memcached, I sent a pull request 3 months ago and I'm still waiting... https://github.com/linsomniac/python-memcached/pull/67 I may fork the project if the maintainer never reply. Read the current thread [all] Non-responsive upstream libraries (python34 specifically) on openstack-dev. (4) python-savannaaclient: We haven't enough tests to ensure that savanna client works correctly on py33, so, it's kind of premature step. We already have py33 and pypy jobs in experimental pipeline. This client can be ported later. Note: The py34 gate of oslo.messaging is currently non voting because of a bug in Python 3.4.0, fix not backported to Ubuntu Trusty LTS yet: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1367907 The bug was fixed in Python 3.4 in May 2014 and was reported to Ubuntu in September 2014. Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
On 07/20/2015 08:26 PM, Brant Knudson wrote: On Fri, Jul 17, 2015 at 7:32 AM, Victor Stinner vstin...@redhat.com mailto:vstin...@redhat.com wrote: Hi, ... (3) keystonemiddleware: blocked by python-memcached, I sent a pull request 3 months ago and I'm still waiting... https://github.com/linsomniac/python-memcached/pull/67 I may fork the project if the maintainer never reply. Read the current thread [all] Non-responsive upstream libraries (python34 specifically) on openstack-dev. ... Victor keystonemiddleware has had a py34 gate for a long time. The tests run without python-memcache installed since the tests are skipped if memcache isn't available. We've got a separate test-requirements-py34.txt that doesn't include python-memcache. This has been causing problems lately since the requirements job now fails since there are duplicate requirements in multiple files (test-requirements-py34 is just test-requirements with python-memcache removed). Well, we should IMO either get rid of python-memcache completely (in the favor of pymemcache), or worse case fork it, since Victor opened a pull request to fix it MONTHS ago. I proposed a change to global-requirements to mark python-memcache as not working on py34: https://review.openstack.org/#/c/203437/ and then we'll have to change keystonemiddleware to merge the test-requirements-py34 into test-requirements: https://review.openstack.org/#/c/197254/ . Hiding the issue will not make it go away. Thomas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
You can (nearly) add Designate to this list :) Pradeep has been doing a great job getting the codebase py3 compatible! Thanks, Kiall On 17/07/15 12:32, Victor Stinner wrote: Hi, We are close to having a voting py34 gate on all OpenStack libraries and applications. I just made the py34 gate voting for the 5 following projects: * keystone * heat * glance_store: Glance library (py34 is already voting in Glance) * os-brick: Cinder library (py34 is already voting in Cinder) * sqlalchemy-migrate A voting py34 gate means that we cannot reintroduce Python 3 regressions in the code tested by tox -e py34. Currently, only a small subset of test suites is executed on Python 3.4, but the subset is growing constantly and it already helps to detect various kinds of Python 3 issues. Sirushti Murugesan (who is porting Heat to Python 3) and me proposed a talk Python 3 is coming! to the next OpenStack Summit at Tokyo. We will explain the plan to port OpenStack to Python in depth. There are only 4 remaining projects without py34 voting gate: (1) swift: I sent patches, see the Fix tox -e py34 patch: https://review.openstack.org/#/q/project:openstack/swift+branch:master+topic:py3,n,z (2) horizon: I sent patches: https://review.openstack.org/#/q/topic:bp/porting-python3+project:openstack/horizon,n,z (3) keystonemiddleware: blocked by python-memcached, I sent a pull request 3 months ago and I'm still waiting... https://github.com/linsomniac/python-memcached/pull/67 I may fork the project if the maintainer never reply. Read the current thread [all] Non-responsive upstream libraries (python34 specifically) on openstack-dev. (4) python-savannaaclient: We haven't enough tests to ensure that savanna client works correctly on py33, so, it's kind of premature step. We already have py33 and pypy jobs in experimental pipeline. This client can be ported later. Note: The py34 gate of oslo.messaging is currently non voting because of a bug in Python 3.4.0, fix not backported to Ubuntu Trusty LTS yet: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1367907 The bug was fixed in Python 3.4 in May 2014 and was reported to Ubuntu in September 2014. Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
Hi, Could you please modify the wiki page yourself to add Designate? I don't want to be the only one maintaining this wiki page ;-) https://wiki.openstack.org/wiki/Python3 Victor - Original Message - From: Kiall Mac Innes ki...@macinnes.ie To: openstack-dev@lists.openstack.org Sent: Tuesday, July 21, 2015 12:51:03 PM Subject: Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing You can (nearly) add Designate to this list :) Pradeep has been doing a great job getting the codebase py3 compatible! Thanks, Kiall On 17/07/15 12:32, Victor Stinner wrote: Hi, We are close to having a voting py34 gate on all OpenStack libraries and applications. I just made the py34 gate voting for the 5 following projects: * keystone * heat * glance_store: Glance library (py34 is already voting in Glance) * os-brick: Cinder library (py34 is already voting in Cinder) * sqlalchemy-migrate A voting py34 gate means that we cannot reintroduce Python 3 regressions in the code tested by tox -e py34. Currently, only a small subset of test suites is executed on Python 3.4, but the subset is growing constantly and it already helps to detect various kinds of Python 3 issues. Sirushti Murugesan (who is porting Heat to Python 3) and me proposed a talk Python 3 is coming! to the next OpenStack Summit at Tokyo. We will explain the plan to port OpenStack to Python in depth. There are only 4 remaining projects without py34 voting gate: (1) swift: I sent patches, see the Fix tox -e py34 patch: https://review.openstack.org/#/q/project:openstack/swift+branch:master+topic:py3,n,z (2) horizon: I sent patches: https://review.openstack.org/#/q/topic:bp/porting-python3+project:openstack/horizon,n,z (3) keystonemiddleware: blocked by python-memcached, I sent a pull request 3 months ago and I'm still waiting... https://github.com/linsomniac/python-memcached/pull/67 I may fork the project if the maintainer never reply. Read the current thread [all] Non-responsive upstream libraries (python34 specifically) on openstack-dev. (4) python-savannaaclient: We haven't enough tests to ensure that savanna client works correctly on py33, so, it's kind of premature step. We already have py33 and pypy jobs in experimental pipeline. This client can be ported later. Note: The py34 gate of oslo.messaging is currently non voting because of a bug in Python 3.4.0, fix not backported to Ubuntu Trusty LTS yet: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1367907 The bug was fixed in Python 3.4 in May 2014 and was reported to Ubuntu in September 2014. Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
On Fri, Jul 17, 2015 at 7:32 AM, Victor Stinner vstin...@redhat.com wrote: Hi, ... (3) keystonemiddleware: blocked by python-memcached, I sent a pull request 3 months ago and I'm still waiting... https://github.com/linsomniac/python-memcached/pull/67 I may fork the project if the maintainer never reply. Read the current thread [all] Non-responsive upstream libraries (python34 specifically) on openstack-dev. ... Victor keystonemiddleware has had a py34 gate for a long time. The tests run without python-memcache installed since the tests are skipped if memcache isn't available. We've got a separate test-requirements-py34.txt that doesn't include python-memcache. This has been causing problems lately since the requirements job now fails since there are duplicate requirements in multiple files (test-requirements-py34 is just test-requirements with python-memcache removed). I proposed a change to global-requirements to mark python-memcache as not working on py34: https://review.openstack.org/#/c/203437/ and then we'll have to change keystonemiddleware to merge the test-requirements-py34 into test-requirements: https://review.openstack.org/#/c/197254/ . - Brant __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
On Fri, Jul 17, 2015 at 7:32 AM, Victor Stinner vstin...@redhat.com wrote: Hi, We are close to having a voting py34 gate on all OpenStack libraries and applications. I just made the py34 gate voting for the 5 following projects: * keystone ... Victor While there's a py34 gate for keystone, it doesn't actually test much, so let's not declare victory just yet. The short list of tests to run are in keystone's tox.ini[1]. Here's the error I get when I add keystone/tests/unit/backend/domain_config/test_sql.py to the list: http://paste.openstack.org/show/392971/ . So another library that we use that doesn't support py34 is dogpile.cache (or maybe keystone isn't calling it correctly). [1] http://git.openstack.org/cgit/openstack/keystone/tree/tox.ini#n20 Brant __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
Hi, We are close to having a voting py34 gate on all OpenStack libraries and applications. I just made the py34 gate voting for the 5 following projects: * keystone * heat * glance_store: Glance library (py34 is already voting in Glance) * os-brick: Cinder library (py34 is already voting in Cinder) * sqlalchemy-migrate A voting py34 gate means that we cannot reintroduce Python 3 regressions in the code tested by tox -e py34. Currently, only a small subset of test suites is executed on Python 3.4, but the subset is growing constantly and it already helps to detect various kinds of Python 3 issues. Sirushti Murugesan (who is porting Heat to Python 3) and me proposed a talk Python 3 is coming! to the next OpenStack Summit at Tokyo. We will explain the plan to port OpenStack to Python in depth. There are only 4 remaining projects without py34 voting gate: (1) swift: I sent patches, see the Fix tox -e py34 patch: https://review.openstack.org/#/q/project:openstack/swift+branch:master+topic:py3,n,z (2) horizon: I sent patches: https://review.openstack.org/#/q/topic:bp/porting-python3+project:openstack/horizon,n,z (3) keystonemiddleware: blocked by python-memcached, I sent a pull request 3 months ago and I'm still waiting... https://github.com/linsomniac/python-memcached/pull/67 I may fork the project if the maintainer never reply. Read the current thread [all] Non-responsive upstream libraries (python34 specifically) on openstack-dev. (4) python-savannaaclient: We haven't enough tests to ensure that savanna client works correctly on py33, so, it's kind of premature step. We already have py33 and pypy jobs in experimental pipeline. This client can be ported later. Note: The py34 gate of oslo.messaging is currently non voting because of a bug in Python 3.4.0, fix not backported to Ubuntu Trusty LTS yet: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1367907 The bug was fixed in Python 3.4 in May 2014 and was reported to Ubuntu in September 2014. Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
On 17 July 2015 at 23:32, Victor Stinner vstin...@redhat.com wrote: Hi, https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1367907 The bug was fixed in Python 3.4 in May 2014 and was reported to Ubuntu in September 2014. I've just queried and its apparently in review-wait in the Ubuntu trusty upload queue; I'll try to find out if there any unexpected delays there etc. -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3: 5 more projects with a py34 voting gate, only 4 remaing
On 7/17/2015 6:32 AM, Victor Stinner wrote: Hi, We are close to having a voting py34 gate on all OpenStack libraries and applications. I just made the py34 gate voting for the 5 following projects: * keystone * heat * glance_store: Glance library (py34 is already voting in Glance) * os-brick: Cinder library (py34 is already voting in Cinder) * sqlalchemy-migrate If we can get this working then we can make py34 voting/gating in sqlalchemy-migrate: https://review.openstack.org/#/c/202170/ A voting py34 gate means that we cannot reintroduce Python 3 regressions in the code tested by tox -e py34. Currently, only a small subset of test suites is executed on Python 3.4, but the subset is growing constantly and it already helps to detect various kinds of Python 3 issues. Sirushti Murugesan (who is porting Heat to Python 3) and me proposed a talk Python 3 is coming! to the next OpenStack Summit at Tokyo. We will explain the plan to port OpenStack to Python in depth. There are only 4 remaining projects without py34 voting gate: (1) swift: I sent patches, see the Fix tox -e py34 patch: https://review.openstack.org/#/q/project:openstack/swift+branch:master+topic:py3,n,z (2) horizon: I sent patches: https://review.openstack.org/#/q/topic:bp/porting-python3+project:openstack/horizon,n,z (3) keystonemiddleware: blocked by python-memcached, I sent a pull request 3 months ago and I'm still waiting... https://github.com/linsomniac/python-memcached/pull/67 I may fork the project if the maintainer never reply. Read the current thread [all] Non-responsive upstream libraries (python34 specifically) on openstack-dev. (4) python-savannaaclient: We haven't enough tests to ensure that savanna client works correctly on py33, so, it's kind of premature step. We already have py33 and pypy jobs in experimental pipeline. This client can be ported later. Note: The py34 gate of oslo.messaging is currently non voting because of a bug in Python 3.4.0, fix not backported to Ubuntu Trusty LTS yet: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1367907 The bug was fixed in Python 3.4 in May 2014 and was reported to Ubuntu in September 2014. Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3 is dead, long live Python 3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2015 05:15 PM, Jeremy Stanley wrote: After a long wait and much testing, we've merged a change[1] which moves the remainder of Python 3.3 based jobs to Python 3.4. This is primarily in service of getting rid of the custom workers we implemented to perform 3.3 testing more than a year ago, since we can now run 3.4 tests on normal Ubuntu Trusty workers (with the exception of a couple bugs[2][3] which have caused us to temporarily suspend[4] Py3K jobs for oslo.messaging and oslo.rootwrap). I've personally tested `tox -e py34` on every project hosted in our infrastructure which was gating on Python 3.3 jobs and they all still work, so you shouldn't see any issues arise from this change. If you do, however, please let the Infrastructure team know about it as soon as possible. Thanks! [1] https://review.openstack.org/151713 [2] https://launchpad.net/bugs/1367907 [3] https://launchpad.net/bugs/1382607 [4] http://lists.openstack.org/pipermail/openstack-dev/2015-January/055270.html The switch broke Icehouse stable branch for oslo-incubator [1] since those jobs run on Precise and not Trusty. Anyone has ideas how to fix it? [1]: https://review.openstack.org/#/c/136718/ /Ihar -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJU9a+VAAoJEC5aWaUY1u57mv4H/0Wqi986LUPYzQCQCzcvHlAv Uomd8cvWNYBUzLJjV2r3xrgaKDVsKtJI+vcMllBNH7oigRHXDo6RrkUoV+4jSf4o yzYtU9CXLO/vKuTnJVzsp3xCuu9XI9mE19FHWLYOAhpSFXNg4J6u94yKRIxxcs6H IAaJEuhcJigm7qK10iKESYvw9AxJjZsHaq0No5KsAT+T5FTmfGZ2cbPfkKSo9NgM Zl0gbPTQPSoB8EvefoP8uaUYF1sD+Itgab1GvI6B9sRnkb+f1uaWAA852SaxiA1D Z5IQOwYCPteBJ1ztSrFAQGw8nfgp8H0I3aHwQ/7fgdxPPb8Eqa/wWHlfUnt0nG4= =ZGSJ -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3 is dead, long live Python 3
On Tue, Mar 3, 2015, at 07:56 AM, Ihar Hrachyshka wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2015 05:15 PM, Jeremy Stanley wrote: After a long wait and much testing, we've merged a change[1] which moves the remainder of Python 3.3 based jobs to Python 3.4. This is primarily in service of getting rid of the custom workers we implemented to perform 3.3 testing more than a year ago, since we can now run 3.4 tests on normal Ubuntu Trusty workers (with the exception of a couple bugs[2][3] which have caused us to temporarily suspend[4] Py3K jobs for oslo.messaging and oslo.rootwrap). I've personally tested `tox -e py34` on every project hosted in our infrastructure which was gating on Python 3.3 jobs and they all still work, so you shouldn't see any issues arise from this change. If you do, however, please let the Infrastructure team know about it as soon as possible. Thanks! [1] https://review.openstack.org/151713 [2] https://launchpad.net/bugs/1367907 [3] https://launchpad.net/bugs/1382607 [4] http://lists.openstack.org/pipermail/openstack-dev/2015-January/055270.html The switch broke Icehouse stable branch for oslo-incubator [1] since those jobs run on Precise and not Trusty. Anyone has ideas how to fix it? The incubator python 3 job was added to help us port incubated code to python 3 before graduating it. We won't be graduating modules from the stable branch, so as long as none of the consuming projects have python 3 jobs on their stable branches we can just drop the icehouse python 3 job for oslo-incubator. Doug [1]: https://review.openstack.org/#/c/136718/ /Ihar -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJU9a+VAAoJEC5aWaUY1u57mv4H/0Wqi986LUPYzQCQCzcvHlAv Uomd8cvWNYBUzLJjV2r3xrgaKDVsKtJI+vcMllBNH7oigRHXDo6RrkUoV+4jSf4o yzYtU9CXLO/vKuTnJVzsp3xCuu9XI9mE19FHWLYOAhpSFXNg4J6u94yKRIxxcs6H IAaJEuhcJigm7qK10iKESYvw9AxJjZsHaq0No5KsAT+T5FTmfGZ2cbPfkKSo9NgM Zl0gbPTQPSoB8EvefoP8uaUYF1sD+Itgab1GvI6B9sRnkb+f1uaWAA852SaxiA1D Z5IQOwYCPteBJ1ztSrFAQGw8nfgp8H0I3aHwQ/7fgdxPPb8Eqa/wWHlfUnt0nG4= =ZGSJ -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3 is dead, long live Python 3
On 2015-02-03 08:15:39 -0500 (-0500), Victor Stinner wrote: [...] Debian Testing (Jessie) and Unstable (Sid) provide Python 3.4.2. [...] Yep, I'm playing now with the possibility to run jobs on Debian Jessie, but due to circumstances with the providers who donate computing resource to us I'm first having to make some more significant changes to our node build tooling (changes we wanted to make anyway, this just steps up the timetable a little). -- Jeremy Stanley __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3 is dead, long live Python 3
Hi, It's good to move forward to Python 3.4 :-) [2] https://launchpad.net/bugs/1367907 This bug was introduced in Python 3.4.0 and fixed in Python 3.4.1. It's too bad that Ubunbu Trusty didn't upgraded yet Python 3.4 to 3.4.1 (released 6 months ago) or 3.4.2. Request to upgrade python 3.4 in Ubuntu Trusty: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1348954 (upgrade already scheduled at the end of february, after the release of python 3.4.3) Debian Testing (Jessie) and Unstable (Sid) provide Python 3.4.2. Debian Stable (Wheezy) only provides Python 3.2.3 (which doesn't accept uunicode syntax :-/ and doesn't support yield-from). Fedora 21 provides Python 3.4.1. (Fedora 20 only provides Python 3.3.2). Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Python 3 is dead, long live Python 3
After a long wait and much testing, we've merged a change[1] which moves the remainder of Python 3.3 based jobs to Python 3.4. This is primarily in service of getting rid of the custom workers we implemented to perform 3.3 testing more than a year ago, since we can now run 3.4 tests on normal Ubuntu Trusty workers (with the exception of a couple bugs[2][3] which have caused us to temporarily suspend[4] Py3K jobs for oslo.messaging and oslo.rootwrap). I've personally tested `tox -e py34` on every project hosted in our infrastructure which was gating on Python 3.3 jobs and they all still work, so you shouldn't see any issues arise from this change. If you do, however, please let the Infrastructure team know about it as soon as possible. Thanks! [1] https://review.openstack.org/151713 [2] https://launchpad.net/bugs/1367907 [3] https://launchpad.net/bugs/1382607 [4] http://lists.openstack.org/pipermail/openstack-dev/2015-January/055270.html -- Jeremy Stanley signature.asc Description: Digital signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3 compatibility
Hi Julien, 2014-02-03 Julien Danjou jul...@danjou.info: There's https://wiki.openstack.org/wiki/Python3 but it's not (always) up to date. Thanks for the pointer, really helpful about the status for the main projects and some key hints. The interest never decreased, but it's always have been a long term effort and it's not going to be finished tomorrow. There's a team of people working among OpenStack projects to add support of Python 3 in various places already, and some clients are already working. Yep, I know there is a team, but from my POV, it seems the visibility of this group decreased over the last months. AIUI, there are no more regular meetings on IRC. Ideally, I'm asking for a team because I would love having gurus helping me driving Python 3 compatibility on Climate. One of the main blocker has been oslo-incubator which was not ported to Python. But if my plan comes together, we'll be able to partially gate on py33 this week. Cool, great info, let us know when the gate is in place. Last, but not least, trollius has been created by Victor Stinner, who actually did that work with porting OpenStack in mind and as the first objective. Yup, and I really appreciate the effort of backporting asyncio to Py2.6. That said, I think it would definitely be a good move to use asyncio directly as it will be stdlib starting with Py3.4 Trollius on the other hand is only supported by one people at the moment. I'm not saying it will still be the same in the next future, especially if Openstack does the choice of trollius for replacing eventlet, but right now, I can't consider it as a good remplacement. -Sylvain -- Julien Danjou ;; Free Software hacker ; independent consultant ;; http://julien.danjou.info ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3 compatibility
On Tue, Feb 04 2014, Sylvain Bauza wrote: Yep, I know there is a team, but from my POV, it seems the visibility of this group decreased over the last months. We don't have a marketing subteam yet. AIUI, there are no more regular meetings on IRC. Ideally, I'm asking for a team because I would love having gurus helping me driving Python 3 compatibility on Climate. I don't think you need meeting for that. We stopped the meeting and didn't restored so far because we did not have any point so far to use them to synchronize or discuss rapidly. If you want help, there's this mailing list where you can expose your issue and I'd be happy to answer you. -- Julien Danjou /* Free Software hacker * independent consultant http://julien.danjou.info */ signature.asc Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Python 3 compatibility
Hi, I was at the FOSDEM event this week-end and some interesting talks about asyncio raised my interest about this framework for replacing eventlet. Although there is an experimental port of asyncio for Python 2.6 named trollius [1], I think it would be a good move for having Python 3. I know there were some regular meetings previously, but it seems the interest decreased. Would it make sense to resume this effort and maybe do a quick inventory of what's missing for supporting Python 3.3 ? In particular, which external requirements are still missing Py3 compatibility and what is the status for the Oslo incubated libraries ? Thanks, -Sylvain [1] https://pypi.python.org/pypi/trollius/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3 compatibility
On Mon, Feb 03 2014, Sylvain Bauza wrote: I was at the FOSDEM event this week-end and some interesting talks about asyncio raised my interest about this framework for replacing eventlet. Although there is an experimental port of asyncio for Python 2.6 named trollius [1], I think it would be a good move for having Python 3. I know there were some regular meetings previously, but it seems the interest decreased. Would it make sense to resume this effort and maybe do a quick inventory of what's missing for supporting Python 3.3 ? In particular, which external requirements are still missing Py3 compatibility and what is the status for the Oslo incubated libraries ? There's https://wiki.openstack.org/wiki/Python3 but it's not (always) up to date. The interest never decreased, but it's always have been a long term effort and it's not going to be finished tomorrow. There's a team of people working among OpenStack projects to add support of Python 3 in various places already, and some clients are already working. One of the main blocker has been oslo-incubator which was not ported to Python. But if my plan comes together, we'll be able to partially gate on py33 this week. Last, but not least, trollius has been created by Victor Stinner, who actually did that work with porting OpenStack in mind and as the first objective. -- Julien Danjou ;; Free Software hacker ; independent consultant ;; http://julien.danjou.info signature.asc Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3 compatibility
On Mon, Feb 3, 2014 at 5:29 PM, Julien Danjou jul...@danjou.info wrote: Last, but not least, trollius has been created by Victor Stinner, who actually did that work with porting OpenStack in mind and as the first objective. AFAIK: victor had plans to send a mail about it to the list later this week. Chmouel. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3
Am 24. Juli 2013 18:00:30 schrieb Monty Taylor mord...@inaugust.com: On 07/23/2013 03:02 PM, Brian Curtin wrote: On Jul 23, 2013, at 3:51 PM, Eric Windisch e...@cloudscaling.com mailto:e...@cloudscaling.com wrote: On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton lo...@bacoosta.com mailto:lo...@bacoosta.com wrote: I'm sure this has been asked before, but what exactly is the plan for Python 3 support? Is the plan to support 2 and 3 at the same time? I was looking around for a blue print or something but I can't seem to find anything. I suppose a wiki page is due. This was discussed at the last summit: https://etherpad.openstack.org/havana-python3 The plan is to support Python 2.6+ for the 2..x series and Python 3.3+. This effort has begun for libraries (oslo) and clients. Work is appreciated on the primary projects, but will ultimately become stalled if the library work is not first completed. I'd like to add that at some point in the future it is our desire to drop support for 2.6, as supporting 2.7 and 3.3+ is way easier than also supporting 2.6. At the moment, I believe our main factor on that is the current version of RHEL. Fingers crossed for a new one soon... :) Not to forget SLES ;-) We are also just finishing up getting 3.3 enabled build slaves in the CI gate, so as projects get 3.3 compliant, we should be able to start testing that. FWIW, I came across https://wiki.openstack.org/wiki/Python3Deps and updated routes, which currently works with 3.3. One small step, for free! I'm a newcomer to this list, but I'm a CPython core contributor and am working in Developer Relations at Rackspace, so supporting Python 3 is right up my alley. Excellent! Welcome, glad to have you. ___ 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] Python 3
On 07/23/2013 03:02 PM, Brian Curtin wrote: On Jul 23, 2013, at 3:51 PM, Eric Windisch e...@cloudscaling.com mailto:e...@cloudscaling.com wrote: On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton lo...@bacoosta.com mailto:lo...@bacoosta.com wrote: I'm sure this has been asked before, but what exactly is the plan for Python 3 support? Is the plan to support 2 and 3 at the same time? I was looking around for a blue print or something but I can't seem to find anything. I suppose a wiki page is due. This was discussed at the last summit: https://etherpad.openstack.org/havana-python3 The plan is to support Python 2.6+ for the 2..x series and Python 3.3+. This effort has begun for libraries (oslo) and clients. Work is appreciated on the primary projects, but will ultimately become stalled if the library work is not first completed. I'd like to add that at some point in the future it is our desire to drop support for 2.6, as supporting 2.7 and 3.3+ is way easier than also supporting 2.6. At the moment, I believe our main factor on that is the current version of RHEL. Fingers crossed for a new one soon... :) We are also just finishing up getting 3.3 enabled build slaves in the CI gate, so as projects get 3.3 compliant, we should be able to start testing that. FWIW, I came across https://wiki.openstack.org/wiki/Python3Deps and updated routes, which currently works with 3.3. One small step, for free! I'm a newcomer to this list, but I'm a CPython core contributor and am working in Developer Relations at Rackspace, so supporting Python 3 is right up my alley. Excellent! Welcome, glad to have you. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3
On Wed, 2013-07-24 at 09:31 -0700, Alex Gaynor wrote: I believe Red Hat's new Software Collections things address this issue, this is to the point which Django (which has historically used RHEL as a barometer for when we could drop Pythons) will drop 2.6 in our next release. Yep, that's a very good point. We're as keen as anyone else to get off Python 2.6 and AIUI some folks on our team are hoping to get RDO Havana onto the 2.7 SCL from here: https://fedorahosted.org/SoftwareCollections/ So, assuming nothing crazy crops up, we should be getting close to a point where dropping 2.6 support upstream would not be a big issue for RHEL users. Cheers, Mark. On Wed, Jul 24, 2013 at 9:00 AM, Monty Taylor mord...@inaugust.com wrote: On 07/23/2013 03:02 PM, Brian Curtin wrote: On Jul 23, 2013, at 3:51 PM, Eric Windisch e...@cloudscaling.com mailto:e...@cloudscaling.com wrote: On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton lo...@bacoosta.com mailto:lo...@bacoosta.com wrote: I'm sure this has been asked before, but what exactly is the plan for Python 3 support? Is the plan to support 2 and 3 at the same time? I was looking around for a blue print or something but I can't seem to find anything. I suppose a wiki page is due. This was discussed at the last summit: https://etherpad.openstack.org/havana-python3 The plan is to support Python 2.6+ for the 2..x series and Python 3.3+. This effort has begun for libraries (oslo) and clients. Work is appreciated on the primary projects, but will ultimately become stalled if the library work is not first completed. I'd like to add that at some point in the future it is our desire to drop support for 2.6, as supporting 2.7 and 3.3+ is way easier than also supporting 2.6. At the moment, I believe our main factor on that is the current version of RHEL. Fingers crossed for a new one soon... :) We are also just finishing up getting 3.3 enabled build slaves in the CI gate, so as projects get 3.3 compliant, we should be able to start testing that. FWIW, I came across https://wiki.openstack.org/wiki/Python3Deps and updated routes, which currently works with 3.3. One small step, for free! I'm a newcomer to this list, but I'm a CPython core contributor and am working in Developer Relations at Rackspace, so supporting Python 3 is right up my alley. Excellent! Welcome, glad to have you. ___ 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] Python 3
On Jul 23, 2013, at 4:32 PM, Doug Hellmann doug.hellm...@dreamhost.commailto:doug.hellm...@dreamhost.com wrote: On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton lo...@bacoosta.commailto:lo...@bacoosta.com wrote: I'm sure this has been asked before, but what exactly is the plan for Python 3 support? Is the plan to support 2 and 3 at the same time? I was looking around for a blue print or something but I can't seem to find anything. If Python 3 support is part of the plan, can I start running 2to3 and making edits to keep changes compatible with Python 2? Eric replied with details, but I wanted to address the question of 2to3. Using 2to3 is no longer the preferred way to port to Python 3. With changes that landed in 3.3, it is easier to create code that will run under python 2.7 and 3.3, without resorting to the translation steps that were needed for 3.0-3.2. Chuck Short has landed a series of patches modifying code by hand for some cases (mostly print and exceptions) and by using the six library in others (for iteration and module renaming). Speaking of preferred ways to port, has there been any discussion about which version takes precedence when we have to do different things? For example, with imports, should we be trying the 2.x name first and falling back to 3.x on ImportError, or vice versa? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3
Speaking of preferred ways to port, has there been any discussion about which version takes precedence when we have to do different things? For example, with imports, should we be trying the 2.x name first and falling back to 3.x on ImportError, or vice versa? Are we having it now? My belief here is we should be following the principle of ask forgiveness, not permission. Try Python 3 and then fallback to Python 2 whenever possible. -- Regards, Eric Windisch ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3
On Jul 24, 2013, at 1:27 PM, Eric Windisch e...@cloudscaling.commailto:e...@cloudscaling.com wrote: Speaking of preferred ways to port, has there been any discussion about which version takes precedence when we have to do different things? For example, with imports, should we be trying the 2.x name first and falling back to 3.x on ImportError, or vice versa? Are we having it now? My belief here is we should be following the principle of ask forgiveness, not permission. Try Python 3 and then fallback to Python 2 whenever possible. That's my belief and preference as well. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Python 3
I'm sure this has been asked before, but what exactly is the plan for Python 3 support? Is the plan to support 2 and 3 at the same time? I was looking around for a blue print or something but I can't seem to find anything. If Python 3 support is part of the plan, can I start running 2to3 and making edits to keep changes compatible with Python 2? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Python 3
On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton lo...@bacoosta.comwrote: I'm sure this has been asked before, but what exactly is the plan for Python 3 support? Is the plan to support 2 and 3 at the same time? I was looking around for a blue print or something but I can't seem to find anything. If Python 3 support is part of the plan, can I start running 2to3 and making edits to keep changes compatible with Python 2? Eric replied with details, but I wanted to address the question of 2to3. Using 2to3 is no longer the preferred way to port to Python 3. With changes that landed in 3.3, it is easier to create code that will run under python 2.7 and 3.3, without resorting to the translation steps that were needed for 3.0-3.2. Chuck Short has landed a series of patches modifying code by hand for some cases (mostly print and exceptions) and by using the six library in others (for iteration and module renaming). Doug ___ 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] Python 3
On Jul 23, 2013, at 3:51 PM, Eric Windisch e...@cloudscaling.commailto:e...@cloudscaling.com wrote: On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton lo...@bacoosta.commailto:lo...@bacoosta.com wrote: I'm sure this has been asked before, but what exactly is the plan for Python 3 support? Is the plan to support 2 and 3 at the same time? I was looking around for a blue print or something but I can't seem to find anything. I suppose a wiki page is due. This was discussed at the last summit: https://etherpad.openstack.org/havana-python3 The plan is to support Python 2.6+ for the 2.x series and Python 3.3+. This effort has begun for libraries (oslo) and clients. Work is appreciated on the primary projects, but will ultimately become stalled if the library work is not first completed. FWIW, I came across https://wiki.openstack.org/wiki/Python3Deps and updated routes, which currently works with 3.3. One small step, for free! I'm a newcomer to this list, but I'm a CPython core contributor and am working in Developer Relations at Rackspace, so supporting Python 3 is right up my alley. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
