[Python-Dev] Preparing 2.0.1

[Martin v. Loewis]

> So how should requests for patches be submitted?
> Should I enter them into the wiki, post to python-dev,
> email to aahz?

Personally, I think 2.0.1 should be primarily driven by user requests;
I think this is also the spirit of the PEP. I'm not even sure that
going over the entire code base systematically and copying all bug
fixes is a good idea.

In that sense, having somebody collect these requests is probably the
right approach. In this specific case, I'll take care of them, unless
somebody else proposes a different procedure. For the record, you are
requesting inclusion of

rev 1.23 of PC/getpathp.c
rev 2.21, 2.22 of Objects/rangeobject.c
rev 1.20 of Lib/test/test_b2.py

Interestingly enough, 2.22 of rangeobject.c also adds three attributes
to the xrange object: start, stop, and step. That is clearly a new
feature, so should it be moved into 2.0.1? Otherwise, the fix must be
back-ported to 2.0.

I think it we need a policy decision here, which could probably take
one of three outcomes:
1. everybody with CVS commit access can decide to move patches from
   the mainline to the branch. That would mean I could move these
   patches, and Fredrik Lundh could install the sre code base as-is.

2. the author of the original patch can make that decision. That would
   mean that Fredrik Lundh can still install his code as-is, but I'd
   have to ask Fred's permission.

3. the bug release coordinator can make that decision. That means that
   Aahz must decide.

If it is 1 or 2, some guideline is probably needed as to what exactly
is suitable for inclusion into 2.0.1. Guido has requested "*pure*
bugfixes", which, to me, says

a) sre must be carefully reviewed change for change
b) the three attributes on xrange objects must not appear in 2.0.1

In any case, I'm in favour of a much more careful operation for a
bugfix release. That probably means not all bugs that have been fixed
already will be fixed in 2.0.1; I would not expect otherwise.

Regards,
Martin