Issue 1235569: Inconsistent singleton constructor messages (original) (raw)

Created on 2005-07-10 12:18 by ppergame, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (6)
msg25782 - (view) Author: Pavel Pergamenshchik (ppergame) Date: 2005-07-10 12:18
Inconsistent TypeError strings: >>> types.NoneType() Traceback (most recent call last): File "", line 1, in ? TypeError: cannot create 'NoneType' instances >>> types.EllipsisType() Traceback (most recent call last): File "", line 1, in ? TypeError: cannot create 'ellipsis' instances
msg25783 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2005-07-10 13:28
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.
msg25784 - (view) Author: Pavel Pergamenshchik (ppergame) Date: 2005-07-11 18:30
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.
msg25785 - (view) Author: Tim Peters (tim.peters) * (Python committer) Date: 2005-07-11 20:17
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.
msg25786 - (view) Author: Pavel Pergamenshchik (ppergame) Date: 2005-07-11 20:22
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.
msg25787 - (view) Author: Tim Peters (tim.peters) * (Python committer) Date: 2005-07-11 20:43
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.
History
Date User Action Args
2022-04-11 14:56:12 admin set github: 42179
2005-07-10 12🔞39 ppergame create