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 brett.cannon
Recipients Jim Fasarakis-Hilliard, Julian, Sean.Ochoa, brett.cannon, eamanu, eric.araujo, ezio.melotti, ncoghlan, petri.lehtinen, rhettinger, serhiy.storchaka, terry.reedy, vstinner
Date 2017-05-27.19:51:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1495914660.45.0.204322015441.issue13349@psf.upfronthosting.co.za>
In-reply-to
Content
I'm fine with not changing this, but I did want to say that I don't think you're guaranteed to have access to the object that triggered the ValueError. If the value that is searched for is in some extension module where it's calculated using C code then you have no way of accessing that value unless the extension module was nice enough to provide the object in the exception, give the repr in the exception message, or document how exactly the transformation from input to what you searched for is.
History
Date User Action Args
2017-05-27 19:51:00brett.cannonsetrecipients: + brett.cannon, rhettinger, terry.reedy, ncoghlan, vstinner, ezio.melotti, eric.araujo, Julian, petri.lehtinen, serhiy.storchaka, Sean.Ochoa, Jim Fasarakis-Hilliard, eamanu
2017-05-27 19:51:00brett.cannonsetmessageid: <1495914660.45.0.204322015441.issue13349@psf.upfronthosting.co.za>
2017-05-27 19:51:00brett.cannonlinkissue13349 messages
2017-05-27 19:51:00brett.cannoncreate