Stowage/cpython
2
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2026-01-04 14:32:21 +00:00
Code Issues Projects Releases Packages Wiki Activity

gh-129407: Clarify that a SystemError isn't always CPython's fault (#129410)

Browse source
This commit is contained in:
Peter Bierma 2025-02-03 06:46:13 -05:00 • committed by GitHub
parent 632ca56821
commit 39b754a359
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

8
Doc/library/exceptions.rst
View file

@ -562,9 +562,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