[Idle-dev] Some implemented ideas that may help IDLE, request for feedback

Michael Foord fuzzyman at voidspace.org.uk
Mon Aug 17 16:02:46 CEST 2009

Tal Einat wrote:
> [snip...]
>>> * Bring IDLE's shell forward on first thing printed to sys.stderr,
>>> this can only happen again after a shell restart. I consider this of
>>> great importance when writing programs that may open other windows,
>>> like a Tkinter program, or a Visual one, since the user might expect
>>> something to happen on that window but nothing happens because of an
>>> error that occurred without him noticing. As reported by Bruce, the
>>> lack of this feature has been a big problem in courses where novices
>>> write such programs and don't understand why an animation has stopped,
>>> because the error message is behind other windows.
>> -0  (doesn't this mean having to *constantly* move the window out of the way
>> when your logging code causes it to jump in front of your GUI)
> ... which would teach users to only log actual errors to stderr.
> +1

Really? Even in libraries they didn't write?

Deliberately pissing off users, even in the name of teaching them good 
habits, is never a good strategy.



More information about the IDLE-dev mailing list