This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients JBernardo, ezio.melotti, ned.deily, terry.reedy
Date 2011-10-16.07:18:44
SpamBayes Score 2.5834984e-06
Marked as misclassified No
Message-id <1318749525.21.0.911065268356.issue13153@psf.upfronthosting.co.za>
In-reply-to
Content
> I would consider it preferable if it quit 

Note that if we catch the error there might be no reason for IDLE to quit (unless the error left IDLE in some invalid state).

> with an error traceback that gave as much info as available,

That might scare newbies away.

> or if there is none, just said "IDLE has met an unexpected problem.", 

So this might be better for all the cases.

> perhaps followed by something like "Pleaee note the circumstances and
> make a report of the tracker is there is none already."

The first message could offer a "Report the problem" option that links to the tracker.  In theory we could also have a way to auto-fill the tracker issue, but that might lead to duplicates.
History
Date User Action Args
2011-10-16 07:18:45ezio.melottisetrecipients: + ezio.melotti, terry.reedy, ned.deily, JBernardo
2011-10-16 07:18:45ezio.melottisetmessageid: <1318749525.21.0.911065268356.issue13153@psf.upfronthosting.co.za>
2011-10-16 07:18:44ezio.melottilinkissue13153 messages
2011-10-16 07:18:44ezio.melotticreate