[Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2 - is this documented?)

Nick Coghlan ncoghlan at gmail.com
Wed Mar 9 12:05:20 CET 2011

On Wed, Mar 9, 2011 at 1:15 AM, Stefan Behnel <stefan_ml at 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.


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list