[issue32438] PyLong_ API cleanup

2019-12-28 Thread Mark Dickinson
Mark Dickinson added the comment: Closing as a duplicate of #36048 (which isn't quite right, since this issue came first, but it's probably close enough). -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Deprecate implicit truncating when convert

[issue32438] PyLong_ API cleanup

2019-12-28 Thread Mark Dickinson
Mark Dickinson added the comment: @Batuhan: I think so, yes; at least, the "deprecated" part is done. The "eventually removed" is not, and I don't know whether we have a target version for that removal. -- ___ Python tracker

[issue32438] PyLong_ API cleanup

2019-12-28 Thread Batuhan
Batuhan added the comment: Is this related/resolved with issue 36048? -- nosy: +BTaskaya ___ Python tracker ___ ___ Python-bugs-lis

[issue32438] PyLong_ API cleanup

2017-12-28 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: See also issue17576. And there may be other related issues. -- nosy: +lemburg, mark.dickinson, serhiy.storchaka, stutzbach versions: +Python 3.7 ___ Python tracker

[issue32438] PyLong_ API cleanup

2017-12-28 Thread Erik Bray
New submission from Erik Bray : Per Serhiy's comment in this thread https://mail.python.org/pipermail/python-ideas/2017-December/048413.html (which I agree with), several of the PyLong_ functions have behavior carried over from Python 2 of calling __int__ on their arguments if the input is not