[goals][Drop Python 2.7 Support] Week R-22 Update
Hello Everyone, Below is the progress on "Drop Python 2.7 Support" for R-22 week. Schedule: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#sch... * I am adding this in Ussuri schedule page[1] Highlights: ======== * We crossed the Milestone-1 and with that, we are in phase-2 of py2 drop which targets all the common libraries and testing tools can start dropping the py2 support. * All the services should drop the py2 but this time. Patches are already up, review and merge them before gate starts failing due to cross projects py2 drop. * I pushed the patches on specs repo to cleanup py2 specific requirement or tox or zuul changes. many projects were running 'openstack-tox-py27' which I have changed to 'openstack-tox-pep8' instead of moving them to py3. pep8 job is enough for Specs repo. * I saw many spec repo failing their docs job due to oslosphinx and incompatible version of yasfb[2]. We need to fix this along with py2 drop patches if existing spec repo running py2 job. NOTE: Phase-2 is for Library (including client library), QA tooling. Phase-3 is mainly for openstack/requirement and audit to all repo. (we can always adjust the schedule to make it smooth migration. For example, dropping a few testing jobs from phase-2/3 candidates if any cross-testing jobs are failing due to phase-1 candidates dropping the support[3].) Summary: ======= The OpenStack services have not merged the py2 drop patches: * Adjutant * Barbican * Designate * ec2-api * Glance * Neutron (stadium projects) * Freezer * Kolla * Karbor * Congress * Storlets * Sahara * Blazar * Masakari * Tacker * Trove (trove-dashbaord patch is not mergd) * Zaqar * Qinling * Tricircle * openstack-helm * python-openstackclient How you can help: ============== - Review the patches. Push the patches if I missed any repo targetted for phase-1. [1] https://review.opendev.org/#/c/699008/ [2] https://review.opendev.org/#/c/698998/ [3] http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011392.... [4] https://review.opendev.org/#/q/topic:drop-py27-support
On 12/14/19 10:29 AM, Ghanshyam Mann wrote:
* I pushed the patches on specs repo to cleanup py2 specific requirement or tox or zuul changes. many projects were running 'openstack-tox-py27' which I have changed to 'openstack-tox-pep8' instead of moving them to py3. pep8 job is enough for Specs repo.
Are you sure? I believe some specs repos are using unit tests to validate that all of the sections of the spec are included (among other things)[0]. I don't think the pep8 job will cover those. 0: https://opendev.org/openstack/nova-specs/src/branch/master/tests/test_titles...
---- On Mon, 16 Dec 2019 13:55:52 -0600 Ben Nemec <openstack@nemebean.com> wrote ----
On 12/14/19 10:29 AM, Ghanshyam Mann wrote:
* I pushed the patches on specs repo to cleanup py2 specific requirement or tox or zuul changes. many projects were running 'openstack-tox-py27' which I have changed to 'openstack-tox-pep8' instead of moving them to py3. pep8 job is enough for Specs repo.
Are you sure? I believe some specs repos are using unit tests to validate that all of the sections of the spec are included (among other things)[0]. I don't think the pep8 job will cover those.
pep8 job keep running the unit tests for many of them via explicit pep8 tox to run the unit tests[1] or not defining the env itself. I can move them to py3 job to be explicitly readable. But for few spec repo like keystone-specs pep8 would not cover the unit tests as pep8 is defined there as pep8 checks only. I will move py2 jobs to py3 job there. Thanks for monitor those. [1] https://opendev.org/openstack/nova-specs/src/commit/36b1b7fbf52360c5e7e335c7... -gmann
0: https://opendev.org/openstack/nova-specs/src/branch/master/tests/test_titles...
participants (3)
-
Ben Nemec
-
Ghanshyam Mann
-
Marcin Juszkiewicz