[infra][stable] python3 is used by default in older stable branches
Hi, The horizon team recently noticed that python3 is used as a default python interpreter in older stable branches like pike or ocata. For example, horizon pep8 job in stable/pike and stable/ocata fails [1][2]. We also noticed that some jobs which are expected to run with python2 (using the tox default interpreter as of the release) are now run with python3 [3]. What is the recommended way to cope with this situation? Individual projects can cope with the default interpreter change repo by repo, but this potentially affects all projects with older stable branches. This is the reason I am sending this mail. Best Regards, Akihiro Motoki (amotoki) [1] https://zuul.opendev.org/t/openstack/build/daaeaedb0a184e29a03eeaae59157c78 [2] https://zuul.opendev.org/t/openstack/build/525dc7f926684e54be8b565a7bbf7193 [3] https://zuul.opendev.org/t/openstack/build/adbc53b8d1f74dac9cd606f4a796c442/...
On 10/01/2020 07.55, Akihiro Motoki wrote:
Hi,
The horizon team recently noticed that python3 is used as a default python interpreter in older stable branches like pike or ocata. For example, horizon pep8 job in stable/pike and stable/ocata fails [1][2]. We also noticed that some jobs which are expected to run with python2 (using the tox default interpreter as of the release) are now run with python3 [3].
Do you know what changed? I don't remember any intended change here, so I'm curious why this happens suddenly. https://zuul.opendev.org/t/openstack/build/0615d1df250144e6a137f0615c25ce66/... from 27th of December already shows this on rocky https://zuul.opendev.org/t/openstack/build/085c0d9ea5d8466099eef3bb0ffb2213 from the 18th of December uses python 2.7. Andreas
What is the recommended way to cope with this situation?
Individual projects can cope with the default interpreter change repo by repo, but this potentially affects all projects with older stable branches. This is the reason I am sending this mail.
Best Regards, Akihiro Motoki (amotoki)
[1] https://zuul.opendev.org/t/openstack/build/daaeaedb0a184e29a03eeaae59157c78 [2] https://zuul.opendev.org/t/openstack/build/525dc7f926684e54be8b565a7bbf7193 [3] https://zuul.opendev.org/t/openstack/build/adbc53b8d1f74dac9cd606f4a796c442/...
-- Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB
On Friday, 10 January 2020 10:50:51 CET Andreas Jaeger wrote:
On 10/01/2020 07.55, Akihiro Motoki wrote:
Hi,
The horizon team recently noticed that python3 is used as a default python interpreter in older stable branches like pike or ocata. For example, horizon pep8 job in stable/pike and stable/ocata fails [1][2]. We also noticed that some jobs which are expected to run with python2 (using the tox default interpreter as of the release) are now run with python3 [3].
Do you know what changed? I don't remember any intended change here, so I'm curious why this happens suddenly.
https://zuul.opendev.org/t/openstack/build/0615d1df250144e6a137f0615c25ce66/ logs from 27th of December already shows this on rocky
https://zuul.opendev.org/t/openstack/build/085c0d9ea5d8466099eef3bb0ffb2213 from the 18th of December uses python 2.7.
Maybe this is related to http://lists.openstack.org/pipermail/openstack-discuss/2019-November/ 010957.html http://eavesdrop.openstack.org/meetings/infra/2019/infra. 2019-11-19-19.05.log.html#l-102 ? Ciao -- Luigi
On 10/01/2020 11.06, Luigi Toscano wrote:
On Friday, 10 January 2020 10:50:51 CET Andreas Jaeger wrote:
On 10/01/2020 07.55, Akihiro Motoki wrote:
Hi,
The horizon team recently noticed that python3 is used as a default python interpreter in older stable branches like pike or ocata. For example, horizon pep8 job in stable/pike and stable/ocata fails [1][2]. We also noticed that some jobs which are expected to run with python2 (using the tox default interpreter as of the release) are now run with python3 [3].
Do you know what changed? I don't remember any intended change here, so I'm curious why this happens suddenly.
https://zuul.opendev.org/t/openstack/build/0615d1df250144e6a137f0615c25ce66/ logs from 27th of December already shows this on rocky
https://zuul.opendev.org/t/openstack/build/085c0d9ea5d8466099eef3bb0ffb2213 from the 18th of December uses python 2.7.
Maybe this is related to http://lists.openstack.org/pipermail/openstack-discuss/2019-November/ 010957.html
that one speaks about Bionic, and these failures are on Xenial nodes. The timing seems of - if it worked on the 18th of December and failed sometime later. thanks, Andreas
http://eavesdrop.openstack.org/meetings/infra/2019/infra. 2019-11-19-19.05.log.html#l-102
?
Ciao
-- Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB
participants (3)
-
Akihiro Motoki
-
Andreas Jaeger
-
Luigi Toscano