Inconsistent TypeError strings:

>>> types.NoneType()
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
TypeError: cannot create 'NoneType' instances
>>> types.EllipsisType()
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
TypeError: cannot create 'ellipsis' instances

Logged In: YES 
user_id=1188172

Where's your problem? If this doesn't cause any
misbehaviour, I recommend closing this as Won't Fix.

Logged In: YES 
user_id=595126

You wouldn't tolerate "TypeError: yuor fanction takes too
mny arguements lol". The inconsistency looks unprofessional
in the same way, if not magnitude.

Logged In: YES 
user_id=31435

ppergame, could you please be explicit about what your 
complaint is here?  I don't know what's bothering you either.  
For example, spell out the text for error messages you think 
would be OK.

Your example:  "fanction takes too mny arguements lol" 
seems meaningless here, since it appears to suggest you 
dislike spelling errors.  That's fine, but there are no spelling 
errors in the messages you're complaining about.

Logged In: YES 
user_id=595126

Either the first error message should be changed to
"TypeError: cannot create 'none' instances" or the second
one should be "TypeError: cannot create 'EllipsisType'
instances".
I apologize for being unclear.

Logged In: YES 
user_id=31435

Ah!  Well, we shouldn't do that -- the messages currently give 
the correct names for the types:

>>> type(None)
<type 'NoneType'>
>>> type(Ellipsis)
<type 'ellipsis'>

The names types are exported under by types.py are pretty 
much arbitrary, but shouldn't be changed either because 
doing so would create backward compatibility headaches.