Skip to content

[3.12] gh-129407: Clarify that a SystemError isn't always CPython's fault (GH-129410) #129611

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Feb 3, 2025
Merged

[3.12] gh-129407: Clarify that a SystemError isn't always CPython's fault (GH-129410) #129611

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions Doc/library/exceptions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -544,9 +544,13 @@ The following exceptions are the exceptions that are usually raised.

Raised when the interpreter finds an internal error, but the situation does not
look so serious to cause it to abandon all hope. The associated value is a
string indicating what went wrong (in low-level terms).
string indicating what went wrong (in low-level terms). In :term:`CPython`,
this could be raised by incorrectly using Python's C API, such as returning
a ``NULL`` value without an exception set.

You should report this to the author or maintainer of your Python interpreter.
If you're confident that this exception wasn't your fault, or the fault of
a package you're using, you should report this to the author or maintainer
of your Python interpreter.
Be sure to report the version of the Python interpreter (``sys.version``; it is
also printed at the start of an interactive Python session), the exact error
message (the exception's associated value) and if possible the source of the
Expand Down
Loading