Nick Coghlan added the comment: As we've started working through the post-release PEP 440 changes, I think this is definitely worthy of a separate PEP. I'll take the opportunity to pitch some other changes as well, like separating out the interoperability standards from the informational PEPs like the CPython release process guide, and add new metadata headers to indicate when the reference implementation of a standard is provided by a project other than CPython.
We may decide the extra complexity isn't worth it, but after wrangling PEP 440 through to completion under the delegation of authority to distutils-sig, I'd at least like to have the discussion about what we think represents a "necessary, but sufficient" level of process change. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23077> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
