[Python-bugs-list] [ python-Bugs-635115 ] int(1e200) should return long
noreply@sourceforge.net
noreply@sourceforge.net
Thu, 14 Nov 2002 15:22:58 -0800
Bugs item #635115, was opened at 2002-11-07 14:02
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=635115&group_id=5470
Category: Type/class unification
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Walter Dörwald (doerwalter)
Assigned to: Nobody/Anonymous (nobody)
Summary: int(1e200) should return long
Initial Comment:
To remove the distinction between int and long
int(1e200) should return a long object instead of
raising an OverflowError.
This is related to bug #629989:
int("123123123123123123") doesn't work.
Fixing this could be done by changing
Objects/floatobject.c/float_int (see attached patch),
but this changes the meaning of the nb_int slot.
----------------------------------------------------------------------
>Comment By: Guido van Rossum (gvanrossum)
Date: 2002-11-14 18:22
Message:
Logged In: YES
user_id=6380
PyInt_AsLong() insists that nb_int returns a PyInt_Object.
I think it's okay that nb_int returns a non-int -- classes
don't require __int__ to do this either. So PyInt_AsLong()
should accept a PyLong_Object as well, I guess.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=635115&group_id=5470