Guido van Rossum added the comment:
Martin, I'm asking you because according to svn blame I copied this from
the int/long integration branch last January.
I looked at the code of _PyLong_FitsInLong(), and I don't understand why
it wants an exact integer. The code
if (!PyLong_CheckExact(vv)) {
PyErr_BadInternalCall();
return 0;
}
can just be omitted IMO, to make this problem go away.
There's no documentation for this function, and the only user
(rangeobject.c()) never checks for an error...
----------
assignee: -> loewis
nosy: +gvanrossum, loewis
__________________________________
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1666>
__________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
