[Python-ideas] stdlib with its own release cycle ?

Tarek Ziadé ziade.tarek at gmail.com
Sun Oct 25 19:43:18 CET 2009

Guido van Rossum schrieb:
> That said a separate stdlib release has been asked for at the language
> summit and I am supportive. But it's link with the moratorium is
> minimal.

On Sun, Oct 25, 2009 at 6:26 PM, Georg Brandl <g.brandl at gmx.net> wrote:
> Anyway, we'll probably get a better picture of what 3.2 will look like
> after the PEP is written and we have a rough release schedule.  Before that
> it's moot to decide on a separate stdlib release.

I guess I'll wait and see then. :)

Here's Distutils use case FYI. I don't know if it can be applied to
other packages in the stdlib but.. :

The work that is being done in Distutils is going to really speed up
once the PEPs we are working on are over and
hopefully accepted, and this package would benefit from a shorter cycle.

The other idea would be to do extra standalone releases of Distutils,
between two Python releases.

I am currently doing nightly builds of the trunk that can be installed
from 2.4 to 3.1 to make it easier for people to try out the current
Distutils trunk. But it's just for testing purposes, because it's
currently using a dirty .pth trick to shadow the existing distutils.


More information about the Python-ideas mailing list