[Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2
Tres Seaver
tseaver at palladion.com
Fri Mar 11 21:53:03 CET 2011
More information about the Python-Dev mailing list
Fri Mar 11 21:53:03 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 ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/11/2011 03:24 PM, Antoine Pitrou wrote: > 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. How would more buildbots help the visibility of changes being landed to the language or standard library? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver at palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk16i68ACgkQ+gerLs4ltQ6RaACeMOXvAqUYByjx5lFUjMcVH0Z9 ZtIAn0MtoBD3LWc6GZsUCrQmL3DJqHVC =rZ+o -----END PGP SIGNATURE-----
- 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