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

Bruce Sherwood Bruce_Sherwood at ncsu.edu
Wed Aug 19 04:30:22 CEST 2009


Tal Einat wrote:
>>> * 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

Could you say a bit more about what Squeezer is or does? How would this 
colorization affect Squeezer?

Bruce Sherwood


More information about the IDLE-dev mailing list