On 2020-07-07 21:35, Barry Warsaw wrote:
It’s true that as releases get closer to final, more people will start
exercising them. However, you really don’t have to wait. I maintain
“official” Linux (Ubuntu) Docker images that contain all the latest releases
(including alphas and betas), and the git head of the development branch at the
time of the image builds.
https://gitlab.com/python-devs/ci-images/-/tree/master
I keep these up-to-date on every new maintenance release, alpha, beta, rc, and
final, for Python 2.7, and 3.4 through 3.10. I use this image in my own open
source code’s CI, and you can too! Unfortunately, we can’t do the same with
Windows, but I’ve cracked the nut to get pretty good coverage for Windows
releases too. Here for example is flufl.lock’s .gitlab-ci.yml file:
https://gitlab.com/warsaw/flufl.lock/-/blob/master/.gitlab-ci.yml
I need to extend that to 3.9 pre-releases, via python.org downloads rather than
nuget.
So, it’s entirely possible to test your stuff against pre-release versions, and
I highly encourage it.
Many of these also get into Fedora (all alphas/betas/RCs go into Rawhide
rather fast; 3.X.0 alphas/betas/RCs go into stable Fedora updates).
And we do our best to build almost 4000 packages with the 3.X.0
alpha/beta/RCs, with many of the builds running test suites.
Unfortunately, "test your stuff" tends to only find regressions. New
features aren't too useful if you need to support stable Python
releases, so they're not tested very much with the betas/RCs.
_______________________________________________
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/3JMRLPUHXKEQVYETL6NZEX6SHAQSEYPG/
Code of Conduct: https://www.python.org/psf/codeofconduct/
