On Wed, Feb 3, 2010 at 05:57, Nick Coghlan firstname.lastname@example.org wrote:
Mark Dickinson wrote:
Agreed on all points. Would it be terrible to simply add all relevant tags the moment a PEP is accepted? E.g., if a PEP pronounces some particular behaviour deprecated in Python 3.3 and removed in Python 3.4, then corresponding release blockers for 3.3 and 3.4 could be opened as part of implementing the PEP.
That strikes me as a really good idea, since the tracker already serves as a global "to do" list for the project (heck, I've used it as a semi-private to do list at times, when I've thought of things I need to fix when I don't have the roundtuits free to actually fix them).
Martin filled me in on how to add new versions, so when we need a new one people can let me know.
-- Nick Coghlan | email@example.com | Brisbane, Australia
Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org