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 Julian
Recipients Julian, r.david.murray, twouters
Date 2013-06-02.02:53:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1370141595.92.0.576645991386.issue18111@psf.upfronthosting.co.za>
In-reply-to
Content
Yes that's a good description. I'm not sure the type of exception is the thing to look at as much as the behavior, I.e. I think next() is a good precedent.

And it's not really pleasant to do this with a try/except. Of course everything's possible, but to catch the ValueError sanely requires checking the text of the exception so that the except isn't too broad.
History
Date User Action Args
2013-06-02 02:53:15Juliansetrecipients: + Julian, twouters, r.david.murray
2013-06-02 02:53:15Juliansetmessageid: <1370141595.92.0.576645991386.issue18111@psf.upfronthosting.co.za>
2013-06-02 02:53:15Julianlinkissue18111 messages
2013-06-02 02:53:15Juliancreate