I think it is more important to have CI that clearly shows the impact of
dev versions of the interpreter and core packages. Some of us in the
Nixpkgs community had this idea for Python core packages as well (and
potentially scientific computing packages, but that's out of scope here).
This would need funding though
https://discuss.python.org/t/funding-for-ci-for-integrating-development-vers...
.
On Fri, Oct 25, 2019 at 4:29 PM Victor Stinner
Hi,
I just posted a new PEP for comments, please reply there, rather than by email: https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539
PEP 608: Coordinated Python release https://www.python.org/dev/peps/pep-0608/
Abstract:
Block a Python release until a compatible version of selected projects is available.
The Python release manager can decide to release Python even if a project is not compatible, if they decide that the project is going to be fixed soon enough, or if the issue severity is low enough.
Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/C3KM3LZI... Code of Conduct: http://python.org/psf/codeofconduct/