Home Original page

[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 22:56:49 CET 2011 
On Fri, 11 Mar 2011 15:53:03 -0500
Tres Seaver <tseaver at palladion.com> wrote:
> -----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?

They would help check that changes don't cause regressions in major
third-party packages such as CPython.

Regards

Antoine.
More information about the Python-Dev mailing list