[Python-Dev] PEP 226
Guido van Rossum
guido@python.org
Sat, 16 Dec 2000 11:38:28 -0500
> I remember earlier discussion on the Python 2.1 release schedule, and
> never managed to comment on those.
>
> I believe that Python contributors and maintainers did an enourmous
> job in releasing Python 2, which took quite some time from everybody's
> life. I think it is unrealistic to expect the same amount of
> commitment for the next release, especially if that release appears
> just a few months after the previous release (that is, one month from
> now).
>
> So I'd like to ask the release manager to take that into
> account. I'm not quite sure what kind of action I expect; possible
> alternatives are:
> - declare 2.1 a pure bug fix release only; with a minimal set of new
> features. In particular, don't push for completion of PEPs; everybody
> should then accept that most features that are currently discussed
> will appear in Python 2.2.
>
> - move the schedule for Python 2.1 back (or is it forward?) by, say, a
> few month. This will people give some time to do the things that did
> not get the right amount of attention during 2.0 release, and will
> still allow to work on new and interesting features.
>
> Just my 0.02EUR,
You're right -- 2.0 (including 1.6) was a monumental effort, and I'm
grateful to all who contributed.
I don't expect that 2.1 will be anywhere near the same amount of work!
Let's look at what's on the table.
0042 Small Feature Requests Hylton
SD 205 pep-0205.txt Weak References Drake
S 207 pep-0207.txt Rich Comparisons Lemburg, van Rossum
S 208 pep-0208.txt Reworking the Coercion Model Schemenauer
S 217 pep-0217.txt Display Hook for Interactive Use Zadka
S 222 pep-0222.txt Web Library Enhancements Kuchling
I 226 pep-0226.txt Python 2.1 Release Schedule Hylton
S 227 pep-0227.txt Statically Nested Scopes Hylton
S 230 pep-0230.txt Warning Framework van Rossum
S 232 pep-0232.txt Function Attributes Warsaw
S 233 pep-0233.txt Python Online Help Prescod