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 rhettinger
Recipients Oren Milman, gvanrossum, mark.dickinson, rhettinger, serhiy.storchaka, vstinner
Date 2017-03-19.00:35:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I don't expect that any code rely on OverflowError. 
> ...
> As MemoryError, it's not common to catch these exceptions.

So why bother making any changes here at all?  It seems like an invented problem resulting in unnecessary churn, creating more work for downstream implementations and test suites.  It isn't even clear that Python will be any better after the change.

One thing I'm strongly against is changing the published C API for things like PyLong_AsUnsignedLong, .  Also, in the content of converting to and from fixed-width C type, an OverflowError seems like exactly the right error.
Date User Action Args
2017-03-19 00:35:25rhettingersetrecipients: + rhettinger, gvanrossum, mark.dickinson, vstinner, serhiy.storchaka, Oren Milman
2017-03-19 00:35:25rhettingersetmessageid: <>
2017-03-19 00:35:25rhettingerlinkissue29833 messages
2017-03-19 00:35:25rhettingercreate