[IronPython] minor issue with types in error messages

Ronnie Maor ronnie.maor at gmail.com
Tue Mar 16 15:11:48 CET 2010


CPython:
>>> None(3)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'NoneType' object is not callable

on IPy 2.6.0:
>>> None(3)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: DynamicNull is not callable

for some reason the type in the error shows up as DynamicNull instead of
NoneType
type(None) looks fine
int behaves similarly.

this doesn't affect me at all, except for scratching my head for a bit
longer when I debugged my code just now, but thought you might want to know.

Ronnie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20100316/898d6be4/attachment.html>


More information about the Ironpython-users mailing list