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

Guilherme Polo ggpolo at gmail.com
Mon Aug 17 16:04:40 CEST 2009

2009/8/17 Tal Einat <taleinat at gmail.com>:
> Michael Foord wrote:
>> Guilherme Polo wrote:
>>> * Terminate the server process under Windows too. On python trunk this
>>> is done only for platforms that support os.kill.
>> +1
> +1 (wasn't such a patch already submitted to the issue tracker?)

I'm not sure about that, maybe I missed it.

>>> * When printing a traceback, highlight the stack traces that pertain
>>> to the running file and also remove the "in <module>" from them. This
>>> is an attempt to make easier for novices to spot probable errors in
>>> their own code.Highlight here simply means that it is written to
>>> stderr, like it is done now, and the other parts are printed to
>>> stdout. The effect normally is that, by default, errors in the primary
>>> file are displayed in red, and other call stack information is blue.
>> +0 (I haven't noticed this problem but will take your word for it)
> I'm a big fan of the Squeezer IDLE extension, and this would break
> Squeezer's recognition of blocks of output / tracebacks. Such (ab)use
> of sys.stdout and sys.stderr is too much of a hack IMHO.
> -1

I see, I definitively need to take a look into Squeezer. It seems to
solve several issues reported on bugs.python.org.

>>> If you would like to try the branch, please do a svn checkout of
>>> http://svn.python.org/view/python/branches/tk_and_idle_maintenance/
>>> It also includes some other fixes and new features not mentioned above.
> I'll definitely give it a go, hopefully tonight or tomorrow after work.

Thanks Tal, I appreciate it.

> - Tal

-- Guilherme H. Polo Goncalves

More information about the IDLE-dev mailing list