Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
gh-130821: Add type information to wrong type error messages#130835
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Drive-by comment: does it make sense to have tests for these changes?
it seems that we don't check the text of error messages if we don't want to check the error type itself |
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I think many of the changes in wording are not clear improvements.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
@@ -1421,17 +1423,17 @@ _PyNumber_Index(PyObject *item) | |||
if (!PyLong_Check(result)) { | |||
PyErr_Format(PyExc_TypeError, | |||
"__index__ returned non-int (type %.200s)", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I don't see much reason to change this error message either.
donBarbosApr 29, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I changed it to the more common way as you recommended elsewhere:__method__() must return an int, not ...
and added type info before method name, like for other methods
@@ -2435,10 +2436,8 @@ method_output_as_list(PyObject *o, PyObject *meth) | |||
PyThreadState *tstate = _PyThreadState_GET(); | |||
if (_PyErr_ExceptionMatches(tstate, PyExc_TypeError)) { | |||
_PyErr_Format(tstate, PyExc_TypeError, | |||
"%.200s.%U() returned a non-iterable (type %.200s)", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Here I strongly prefer the old message. Iterable is not a type, it's a category of types.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
what do you think about new message:"%T.%U() must return an iterable, not %T"
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
I got next output for use case from issue:
but we still have a lot of other places where wrong type errors have inconsistent messages. should they be updated too?