__new__ and __newargs__ don't appear to be documented c.mro() seems to show a circular definition. Please see the examples below: >>> c <type 'int'> >>> c.mro() [<type 'int'>, <type 'object'>] >>> c.__getnewargs__() <method '__getnewargs__' of 'int' objects> >>> c.__getnewargs__(21) Traceback (most recent call last): File "", line 1, in ? TypeError: descriptor '__getnewargs__' of 'int' object needs an argument >>> c.__getnewargs__(21) (21,) >>> c= 1+1j >>> c (1+1j) >>> c.__getnewargs__(21) Traceback (most recent call last): File "", line 1, in ? TypeError: __getnewargs__() takes no arguments (1 given) >>> c.__getnewargs__() ((1+1j),) >>> c.__new__ <built-in method __new__ of type object at 0x1E0B1B40> >>> c.__new__(ComplexType) 0j >>> Colin W.
Logged In: YES user_id=6656 It's hard to make out which specific bug you are reporting, or even if you are reporting a specific bug. Can you please clarify?
Logged In: YES user_id=285587 The first two seem to be missing from the Reference Doc. This third is more a matter of puzzlement. c is of TypeInt c.mro() returns <type 'int'> as the first item in its list.
Logged In: YES user_id=285587 Thanks Michael, mro is defined in the Simionato paper. The key is " including the class itself". The __new__ is not exactly defined, but is clear enough in the GVD paper. I'm afraid I found the material on __getnewargs__ incomprehesible. Could I suggest that a note be put in the main docs that these terms will be defined? Colin W.