Author ned.deily
Recipients JBernardo, ezio.melotti, ned.deily, terry.reedy
Date 2011-10-16.19:40:29
SpamBayes Score 8.83359e-07
Marked as misclassified No
Message-id <1318794030.19.0.867840883944.issue13153@psf.upfronthosting.co.za>
In-reply-to
Content
Just to be sure we're talking about the same thing here, my understanding is that the "missing traceback" issues referred to here are only an issue when IDLE is run as a stand-alone GUI program, such as can be done on Windows and with the OS X IDLE.app.  In that case, the standard Python tracebacks from the interpreter written to stderr are not readily visible to the user.  In the OS X IDLE.app case it does get captured in a system log. I'm not sure if that happens anywhere in the Windows cases.  If IDLE is started from a terminal window or console window where stderr is displayed, this is not an issue.

But I think further discussion about proposed improvements to IDLE diagnostics could be useful but it is not germane to the specific bug here.  It should be carried out elsewhere, possibly resulting in a feature request.
History
Date User Action Args
2011-10-16 19:40:30ned.deilysetrecipients: + ned.deily, terry.reedy, ezio.melotti, JBernardo
2011-10-16 19:40:30ned.deilysetmessageid: <1318794030.19.0.867840883944.issue13153@psf.upfronthosting.co.za>
2011-10-16 19:40:29ned.deilylinkissue13153 messages
2011-10-16 19:40:29ned.deilycreate