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

Guilherme Polo ggpolo at gmail.com
Mon Aug 17 16:13:05 CEST 2009

2009/8/17 Michael Foord <fuzzyman at voidspace.org.uk>:
> 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.

I have no doubt this is a feature that might help some and annoy
others. I still stand on my opinion that it is a good addition, but
making it optional seems really the better way to go.

> Michael
> --
> http://www.ironpythoninaction.com/
> http://www.voidspace.org.uk/blog

-- Guilherme H. Polo Goncalves

More information about the IDLE-dev mailing list