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 Anj-A
Recipients Anj-A, aldwinaldwin, larry, paul.moore, serhiy.storchaka, steve.dower, tim.golden, vstinner, zach.ware, zufuliu
Date 2019-11-12.12:10:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1573560617.09.0.384325224879.issue37436@roundup.psfhosted.org>
In-reply-to
Content
Hey, if there is no bug here, could we get this issue closed?
Alternatively, I'd be interested in doing the required change in documentation/error type if that's seen to be the right solution.

Personally, I think returning False instead of raising an error would indeed mask bugs as mentioned by Zufu. As for the error type to be raised, the argument type itself isn't wrong, it's just greater than the maximum so I feel an OverflowError type is right instead of TypeError. So maybe just clearer documentation is needed as suggested by Aldwin and no code change? Just my two cents though.
History
Date User Action Args
2019-11-12 12:10:17Anj-Asetrecipients: + Anj-A, paul.moore, vstinner, larry, tim.golden, zach.ware, serhiy.storchaka, steve.dower, aldwinaldwin, zufuliu
2019-11-12 12:10:17Anj-Asetmessageid: <1573560617.09.0.384325224879.issue37436@roundup.psfhosted.org>
2019-11-12 12:10:17Anj-Alinkissue37436 messages
2019-11-12 12:10:16Anj-Acreate