Hi All, I'd like to enable py37 unit tests in the gate.
== Background == I work on OpenStack packaging for Ubuntu. During the Rocky release (Ubuntu Cosmic) I tried to fix py37 bugs upstream as I came across them. There ended up being a lot of py37 issues and after a while, due to time constraints, I resorted to just opening bugs and disabling py37 unit tests that were failing in our package builds. Luckily enough, even though Cosmic ships with python3.6 and python3.7, python3.6 ended up being chosen as the default for Cosmic. == Defaulting to python3.7 == The next release of Ubuntu opens in just a few weeks. It will default to python3.7 and will not include python3.6. My hope is that if I can help enable py37 unit tests upstream now, we can get a wider view at fixing issues soon. == Enabling py37 unit tests == Ubuntu Bionic (18.04 LTS) has the 3.7.0 interpreter and I have reviews up to define the py37 zuul job and templates here: https://review.openstack.org/#/c/609066 I'd like to start submitting reviews to projects to enable openstack-python37-jobs (or variant) for projects that already have openstack-python36-jobs in their .zuul.yaml, zuul.yaml, .zuul.d/project.yaml. == Coinciding work == There is python3-first work going on now and I completely understand that this is going to cause more work for some projects. It seems that now is as good of a time as ever to catch up and test with a recent python3 version. I'm sure python3.8 and beyond will be here before we know it. Any thoughts or concerns? Thanks, Corey
__________________________________________________________________________ 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