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 larry
Recipients larry, zach.ware
Date 2014-01-24.22:41:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390603314.89.0.445507180634.issue20381@psf.upfronthosting.co.za>
In-reply-to
Content
It's considered bad form to catch Exception.  We should catch the minimum necessary.  If there are exceptions we forgot, people will complain and then we'll add those.

Also, I want to make sure (if possible) that the value round-trips correctly through eval and repr. We need to repr the value, and if it doesn't round-trip properly the user needs to know.

On the other hand, I'm okay with starting with bad=False and going from there.  The previous block (with DetectBadNodes()) already does that.  Hang on for a patch.
History
Date User Action Args
2014-01-24 22:41:54larrysetrecipients: + larry, zach.ware
2014-01-24 22:41:54larrysetmessageid: <1390603314.89.0.445507180634.issue20381@psf.upfronthosting.co.za>
2014-01-24 22:41:54larrylinkissue20381 messages
2014-01-24 22:41:54larrycreate