[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Mark Dickinson added the comment: Merged relevant bits to py3k in r77220. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Mark Dickinson added the comment: Applied to trunk in r77218. The DeprecationWarning for the 'L' format needs to be merged to py3k. -- versions: +Python 3.2 ___ Python tracker

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Mark Dickinson added the comment: Here's a patch that makes the DeprecationWarning a TypeError, and adds a new DeprecationWarning for the 'L' format. -- keywords: +patch Added file: http://bugs.python.org/file15649/issue5080.patch ___ Python tracker

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Mark Dickinson added the comment: 'h' also produces a DeprecationWarning; I just added the missing tests for it in r76930 (trunk) and r76931 (py3k). -- ___ Python tracker ___ _

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Mark Dickinson added the comment: Hmm. That's unfortunate: for argument type in 'bBHiIlkKn', an attempt to pass a float results in a DeprecationWarning. For type 'L', there's no DeprecationWarning, and the float is silently truncated. So for type 'L' I guess we still have to go through a

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Mark Dickinson added the comment: Yes, checking with python-dev sounds sensible. I'll wait until there's a working patch, though. -- ___ Python tracker ___ _

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Antoine Pitrou added the comment: I think this should be signalled on the mailing-list, by the way. I expect everyone to agree of course :) -- ___ Python tracker ___

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Antoine Pitrou added the comment: +1 for a TypeError too. -- nosy: +pitrou priority: -> normal stage: -> needs patch ___ Python tracker ___

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Changes by Mark Dickinson : -- assignee: -> mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Changes by Marcin Wider : -- nosy: +marcin.wider ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

STINNER Victor added the comment: +10. It would fix the os.urandom(1.2) bug. On Linux, os.urandom() displays the following warnings and then go into an unlimited loop... /usr/lib/python2.5/os.py:734: DeprecationWarning: integer argument expected, got float bytes += read(_urandomfd, n - len(by

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Georg Brandl added the comment: +1. -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

New submission from Mark Dickinson : Since Python 2.3, PyArg_ParseTuple and friends give a DeprecationWarning for floating-point arguments where integers are expected. From http://www.python.org/download/releases/2.3/NEWS.txt: - The PyArg_Parse functions now issue a DeprecationWarning if a floa