Sat, 26 Jul 2003 19:01:54 +0200
On Saturday 26 July 2003 18:45, Aahz wrote:
> Given that the IDLE bug doesn't affect Apple (they don't ship Python
> with Tkinter), I suggest that we not run around like chickens to fix the
> IDLE bug, but plan on a 2.3.1 release by end of August.
> What I'd recommend doing for now is putting a big note on the 2.3
> download page (not on the front page as Anna suggests).
Maybe a reasonable compromise -- download page, "what's new",
and assorted README files. Updating those won't break anything.
Still, passing errors off silently when they've not been explicitly
silenced IS a bug, as well as a violation of the Python Zen -- and
that seems to be what IDLE is currently doing. Documenting the
bug is better than nothing, but putting out a 2.3 release with such
a known bug "because that bug won't affect Apple" (with its whopping,
what, 5% of the market vs Microsoft's 90%+...?) still leaves me a bit
perplexed. Decision up to the release managers, of course, but as
for me personally I'd like 2.3 to have a bit more than just these
updates to python.org & informal docfiles to make the user aware
that [a] socket bugs may be impeding his use of IDLE AND [b] IDLE
is NOT trying to send information out surreptitiously. Not fixing bugs
(that might be too hard to do right now for 2.3 and missing 2.3's deadline
is just not an option) but making sure "cards are on the table"...
> This would also give us time to deal with some other nagging issues for
> the 2.3 release while committing to a relatively short window for
> getting them out.
Yes, this does sound good to me. A short-term 2.3.1 to fix this and
other nags does sound good; I'd just like to see a little bit more about
it in 2.3 proper.