On Dec 19, 7:42 pm, "Gabriel Genellina" <[EMAIL PROTECTED]> wrote: > En Wed, 19 Dec 2007 18:11:49 -0300, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> escribió: > > > > > 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 range(0,a(5)): > > print(x) > > > Which resulted in a: > > > Traceback (most recent call last): > > File "<stdin>", line 1, in <module> > > File "a.py", line 5, in <module> > > for x in range(0,a(5)): > > SystemError: .\Objects\longobject.c:400: bad argument to internal > > function > > > Interesting! > > Yes. But much more interesting would be to report this on the bug tracker > http://bugs.python.orgelse it will fade away... > > -- > Gabriel Genellina
Gabriel, I usually do that... But from what i've learned, most things i've thought are bugs, turn out to be that way for a good reason. I was playing it safe on this one :-) Joseph Armbruster -- http://mail.python.org/mailman/listinfo/python-list
