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 ganesh3597
Recipients ZackerySpytz, ganesh3597, mark.dickinson, serhiy.storchaka
Date 2020-12-19.04:20:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1608351607.15.0.81131639216.issue42665@roundup.psfhosted.org>
In-reply-to
Content
Hi All, thanks for the input. Yeah, the current behavior makes sense, if overflow exception is needed, we can use PyLong_AsLong. I guess my confusion was from the doc: 
> set *overflow to 1 or -1, respectively, and return -1;
> Returns -1 on error. Use PyErr_Occurred() to disambiguate.

It's not particularly clear if overflow is an `error` here, but again a quick compile and run will give you the answer. You can take a call if we have to have an explicit statement saying: no exception raised on overflow
History
Date User Action Args
2020-12-19 04:20:07ganesh3597setrecipients: + ganesh3597, mark.dickinson, serhiy.storchaka, ZackerySpytz
2020-12-19 04:20:07ganesh3597setmessageid: <1608351607.15.0.81131639216.issue42665@roundup.psfhosted.org>
2020-12-19 04:20:07ganesh3597linkissue42665 messages
2020-12-19 04:20:06ganesh3597create