[Python-Dev] Py2.3.1

[Raymond Hettinger]

> > [Raymond Hettinger]
> >> Is it still the plan to have to rapid schedule for the
> >> first bugfix release (perhaps in early September)?

[Tim]
> > AFAIK there's nothing worthy of being called "a plan" for any future
> > release(s).

Let's make a plan so that it doesn't languish.


[Raymond]
> >> I think it will increase the acceptance of 2.3 and help
> >> it to be viewed as stabilized .

[Tim]
> > Me too.  I can't give non-trivial time to closing bugs or patches in the
> > foreseeable future, but can volunteer a night to test and pump out a 3.1
> > Windows installer (unless Thomas Heller wants to do it).

[Thomas Heller]
> I would do it, but I'm on vacation the first two weeks of September.

The third week in September would be a good target date if you
could do it then.

That will leave time for more fixes to get in and be exercised.
Kurt still has a handful of open idle issues, Michael has a few
leaks left to hunt down, and MvL has been on vacation and not
had a chance to review the open bug reports.


[Aahz]
> While I think this is a Good Idea, to my knowledge there isn't any
> particular driver for a speedy release.  I also haven't heard that many
> of the bugs considered important/critical for 2.3.1 have been fixed;

A handful of small disasters were fixed:
* Windows failures when installed on path names with spaces
* Runaway leaks in the socket and array modules
* strptime() running thousands of times slower without caching

All of these are a barrier to 2.3.1 being accepted as stable.


Raymond Hettinger


#################################################################
#################################################################
#################################################################
#####
#####
#####
#################################################################
#################################################################
#################################################################