Nick Coghlan added the comment: The branch status is captured in the release PEPs:
2.6 (& 3.0): https://www.python.org/dev/peps/pep-0361/ 2.7: https://www.python.org/dev/peps/pep-0373/ 3.1: https://www.python.org/dev/peps/pep-0375/ 3.2: https://www.python.org/dev/peps/pep-0392/ 3.3: https://www.python.org/dev/peps/pep-0398/ 3.4: https://www.python.org/dev/peps/pep-0429/ 3.5: https://www.python.org/dev/peps/pep-0478/ 3.6: https://www.python.org/dev/peps/pep-0494/ The "devcycle" page in the developer guide captures the details of the difference phases: https://docs.python.org/devguide/devcycle.html So perhaps the expedient near term solution would be to put this info on the devcycle page, and move it later? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25296> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
