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

[Guido van Rossum]

On Sun, Oct 25, 2009 at 10:26 AM, Georg Brandl <g.brandl at gmx.net> wrote:
> Guido van Rossum schrieb:
>> On Sun, Oct 25, 2009 at 4:56 AM, Georg Brandl <g.brandl at gmx.net> wrote:
>>> Exactly. Since with the moratorium in effect, we are basically changing
>>> *nothing but* the stdlib, it has its own release cycle already :)
>>
>> Not true. There is much core work that can be done without changing
>> the language definition (e.g. removing the GIL, speedups). Also,
>> extension modules written in C presumably don't fall under the
>> separate stdlib release but are excluded from the moratorium.
>
> I'd have counted them among the stdlib.

Hmm, but C extensions don't work with other implementations (at least
not with Jython, IronPython, PyPy).

> You're of course right, other
> core work can and should be done, but it won't be as visible as new stdlib
> modules or improved APIs in there.

Depends. Imagine Unladen Swallow merged in -- it would be huge from
all kinds of perspectives (pro and con, I suppose) but wouldn't change
the language at all.

> 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.

Hm, I think the separate-stdlib-release idea needs separate discussion
quite independent of the moratorium.

-- 
--Guido van Rossum

PS. My elbow needs a couple more weeks of rest. Limiting myself to
ultra-short emails.