-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
Add details for JSON serialization errors #122163
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
type-feature
A feature request or enhancement
Comments
cc @iritkatriel |
serhiy-storchaka
added a commit
to serhiy-storchaka/cpython
that referenced
this issue
Jul 23, 2024
This that allows to identify the source of the error.
serhiy-storchaka
added a commit
to serhiy-storchaka/cpython
that referenced
this issue
Jul 23, 2024
This allows to identify the source of the error.
serhiy-storchaka
added a commit
that referenced
this issue
Jul 23, 2024
This allows to identify the source of the error.
nohlson
pushed a commit
to nohlson/cpython
that referenced
this issue
Jul 24, 2024
…2165) This allows to identify the source of the error.
nohlson
pushed a commit
to nohlson/cpython
that referenced
this issue
Jul 24, 2024
…2165) This allows to identify the source of the error.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature or enhancement
When an JSON unserializable object occurs deeply in the large structure, it is difficult to find the culprit, because the error message by default only contains the type of the unserializable object. This is pretty common error, for example you can forget to convert the datetime object to timestamp or string.
The proposed PR adds notes to the raised exception which allow to identify the source of the error. For example:
Linked PRs
The text was updated successfully, but these errors were encountered: