[Python-Dev] 2.3.1

["Martin v. Löwis"]

Alex Martelli wrote:

> It's been in *idlefork* -- not in the mainstream, an official Python 
> release.  

It's been in 2.3b2. The release candidate is to discover critical bugs
that have been introduced *in that candidate*, not to discover bugs that
had been there before. Beta releases are there to find bugs that had
been introduced during the development cycle.

> The kind of people for whom these problems are very
> serious -- newbies, attracting whom is crucial to Python's future --
> just aren't likely to download and try arbitrary SF projects nor any
> release that's not "final"; 

These are the people for whom that problem is serious. However, if the
problem was really common, it would have been detected during the beta.
So while the problem might be serious if it happens, I still don't
think it happens often. It's not that all, or even most, Win98 
installations are affected.

So far, the actual conditions under which it occurs haven't even been
identified, let alone the problem being understood.

So I suggest to release IDLE as-is, investigating more time into 
understanding both the cause of the problem and the impact in
real life.

Regards,
Martin