On Wed, Mar 9, 2011 at 1:15 AM, Stefan Behnel <stefan...@behnel.de> wrote: > A publicly visible list of those decisions would > > a) make it easier for non-core developers to follow important changes on > python-dev > > b) allow potentially impacted people to bring up their POV more quickly, > e.g. during the alpha cycle of a deprecation release rather than the > following release, as in this case > > c) document the decision taking process by listing the relevant mailing list > threads > > d) help in writing the "what's new" documents
I've wondered myself if we should simply be more inclined to create PEPs for changes with a wide impact, even if they're technically a CPython-specific implementation decision (cf. zipfile/directory execution, migration from PyCObject to PyCapsule API). Both of those were backed by extensive tracker and mailing list discussions, but there's no easy reference point for anyone coming across them later. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.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/archive%40mail-archive.com
