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 gvanrossum
Recipients Oren Milman, gvanrossum, mark.dickinson, rhettinger, serhiy.storchaka, vstinner
Date 2017-03-18.17:07:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If I had to do it over again I would have used OverflowError only for some very narrowly defined conditions and ValueError for "logical" range limitations. In particular OverflowError suggests that the abstraction is slightly broken (since we usually don't think much about how large an integer fits in a register) while ValueError suggests that the caller passed something of the right type but with an inappropriate value.

I'm not too worried about breaking APIs in this case (but that could change if someone finds data showing there are common idioms in actual use that would break).
Date User Action Args
2017-03-18 17:07:02gvanrossumsetrecipients: + gvanrossum, rhettinger, mark.dickinson, vstinner, serhiy.storchaka, Oren Milman
2017-03-18 17:07:02gvanrossumsetmessageid: <>
2017-03-18 17:07:02gvanrossumlinkissue29833 messages
2017-03-18 17:07:02gvanrossumcreate