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 terry.reedy
Recipients kbk, ppperry, roger.serwy, terry.reedy
Date 2015-06-02.23:32:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433287927.27.0.854011162598.issue24252@psf.upfronthosting.co.za>
In-reply-to
Content
Your message arrived as I was just starting on this issue, wondering whether the exclusion of threading and queue blocks is proper and wishing for an easy test example, such as you provided. It verifies the issue in 3.x.  It also answers the question: trimming queue blocks is not acceptible.  (Many threading functions also raise various exceptions.) Informative tracebacks are a major python feature.  So Idle should be conservative about trimming tracebacks.

The attached 3.4 patch solves queue and threading problems by deleting them from the exclude list.  It attempts to solve your pdb problem by conditionally removing bdb.py also.  Could you patch your Idle, by hand if necessary, and test?
History
Date User Action Args
2015-06-02 23:32:07terry.reedysetrecipients: + terry.reedy, kbk, roger.serwy, ppperry
2015-06-02 23:32:07terry.reedysetmessageid: <1433287927.27.0.854011162598.issue24252@psf.upfronthosting.co.za>
2015-06-02 23:32:07terry.reedylinkissue24252 messages
2015-06-02 23:32:06terry.reedycreate