Skip to content

Commit eff45c9

Browse files
[3.12] gh-129407: Clarify that a SystemError isn't always CPython's fault (GH-129410) (#129611)
gh-129407: Clarify that a `SystemError` isn't always CPython's fault (GH-129410) (cherry picked from commit 39b754a) Co-authored-by: Peter Bierma <[email protected]>
1 parent 9709746 commit eff45c9

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

Doc/library/exceptions.rst

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -544,9 +544,13 @@ The following exceptions are the exceptions that are usually raised.
544544

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

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

0 commit comments

Comments
 (0)