[Python-Dev] Need traceback expert to review patch 954922

Anthony Baxter anthony at interlink.com.au
Tue May 18 10:04:15 EDT 2004


Brett C. wrote:
> And the reason I bring this up now is just in case there is any desire 
> to put this in 2.3.4 .  I obviously know that I missed rc1, but I didn't 
> get the details of triggering the problem soon enough and people running 
> 2.3.x are the ones bringing this up since this apparently did not happen 
> under 2.2 for some reason.  I doubt Anthony wants to risk mucking with 
> 'threading' this late (although the patch is fairly self-contained but 
> would require applying the previous patch to attempt to fix this as 
> well), but I thought I would at least put it out there.

Not going to be there for 2.3.4.

My approach to the bug fix releases is that, in general, "there's
always a next release". That is, the bug fix releases are relatively
frequent (5-6 months) and they're "what's in the branch at the moment".

Starting with the next (2.3.5/2.4.1) releases, I plan on sending out
a 1 month warning to python-list/python-dev, so that people that care
can make sure their pet bug fix is checked in and done before the
release. I'm really not interested in trying to slot in last minute
changes that may, or may not, break the release.

In case it wasn't clear, I'm trying to get Python into a nice regular
release cycle for the bugfix releases. While there will be the
occasional "oh. my. god." type bug that drive a bug fix release
now now now, I'd prefer that people can get used to a regular
cycle for the bug fix releases. Part of this, of course, is being
harsh on the no-new-features rule. I want people to feel confident
that a bug fix release won't break their installed code base. In
addition, I never ever want to see

try:
     True, False
except NameError:
     True, False = 1, 0

or it's like ever again. I've seen it far far too often in code that
wants to be "2.2" compatible, but the new True/False in the bugfix
release of 2.2 made life unpleasant.

I'm open to suggestions for this - although emails about "but I really
really want SF bug #XYZ fixed for 2.3.4" is not what I'm after.

Anthony
-- 
Anthony Baxter     <anthony at interlink.com.au>
It's never too late to have a happy childhood.



More information about the Python-Dev mailing list