[Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2
Antoine Pitrou
solipsis at pitrou.net
Fri Mar 11 21:24:37 CET 2011
More information about the Python-Dev mailing list
Fri Mar 11 21:24:37 CET 2011
- Previous message: [Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2 - is this documented?)
- Next message: [Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2 - is this documented?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 09 Mar 2011 07:15:07 +0100 Stefan Behnel <stefan_ml at behnel.de> wrote: > > Actually, why not put up a web page of "upcoming changes" somewhere, that > lists major decisions with user impact that were taken on python-dev? > Including a link to the relevant discussion and decision. Often enough, > decisions are taken inside of huge mailing list threads that get off-topic > before someone has "the right idea" and everyone who's still there to > listen agrees. Even for people lurking around on python-dev, it's easy > enough to miss these moments. A better alternative IMHO would be to revive the community buildbots (pybots.org), under the same form or another. Regards Antoine.
- Previous message: [Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2 - is this documented?)
- Next message: [Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2 - is this documented?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list