Martin v. Löwis added the comment:
As of r59585, _PyLong_FitsInLong() is no longer.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1666
__
New submission from Joseph Armbruster:
I was wondering what would happen, so I tried this out for the heck of
it with:
Python 3.0a2 (py3k:59572M, Dec 19 2007, 15:54:07) [MSC v.1500 32 bit
(Intel)]
on win32
class a(int):
def __new__(cls,number):
return int.__new__(cls,number)
for x in
Changes by Joseph Armbruster:
--
type: crash - behavior
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1666
__
___
Python-bugs-list mailing list
Unsubscribe:
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
