[IronPython] minor issue with types in error messages

[Dino Viehland]

We're picking up the .NET type name (we have a .NET type to represent NoneType) not the Python type name.  You can also see it with ""() where we report String is not callable.  It's simple enough to fix.

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Ronnie Maor
Sent: Tuesday, March 16, 2010 7:12 AM
To: Discussion of IronPython
Subject: [IronPython] minor issue with types in error messages

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/a5a9543d/attachment.html>