bpo-6634: [doc] clarify that sys.exit() does not always exit the interpreter (GH-31639) (GH-31661)

(cherry picked from commit 10117f1d8cb49ce95493555c06050faf636ccee7)

Co-authored-by: vidhya <96202776+Vidhyavinu@users.noreply.github.com>

Co-authored-by: vidhya <96202776+Vidhyavinu@users.noreply.github.com>
This commit is contained in:
Miss Islington (bot) 2022-03-03 07:16:23 -08:00 committed by GitHub
parent 1d428bb8c9
commit 09819863a3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -412,10 +412,7 @@ always available.
.. function:: exit([arg])
Exit from Python. This is implemented by raising the :exc:`SystemExit`
exception, so cleanup actions specified by finally clauses of :keyword:`try`
statements are honored, and it is possible to intercept the exit attempt at
an outer level.
Raise a :exc:`SystemExit` exception, signaling an intention to exit the interpreter.
The optional argument *arg* can be an integer giving the exit status
(defaulting to zero), or another type of object. If it is an integer, zero
@ -432,7 +429,8 @@ always available.
Since :func:`exit` ultimately "only" raises an exception, it will only exit
the process when called from the main thread, and the exception is not
intercepted.
intercepted. Cleanup actions specified by finally clauses of :keyword:`try` statements
are honored, and it is possible to intercept the exit attempt at an outer level.
.. versionchanged:: 3.6
If an error occurs in the cleanup after the Python interpreter