Skip to content

Commit 0981986

Browse files
bpo-6634: [doc] clarify that sys.exit() does not always exit the interpreter (GH-31639) (GH-31661)
(cherry picked from commit 10117f1) Co-authored-by: vidhya <[email protected]> Co-authored-by: vidhya <[email protected]>
1 parent 1d428bb commit 0981986

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

Doc/library/sys.rst

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -412,10 +412,7 @@ always available.
412412

413413
.. function:: exit([arg])
414414

415-
Exit from Python. This is implemented by raising the :exc:`SystemExit`
416-
exception, so cleanup actions specified by finally clauses of :keyword:`try`
417-
statements are honored, and it is possible to intercept the exit attempt at
418-
an outer level.
415+
Raise a :exc:`SystemExit` exception, signaling an intention to exit the interpreter.
419416

420417
The optional argument *arg* can be an integer giving the exit status
421418
(defaulting to zero), or another type of object. If it is an integer, zero
@@ -432,7 +429,8 @@ always available.
432429

433430
Since :func:`exit` ultimately "only" raises an exception, it will only exit
434431
the process when called from the main thread, and the exception is not
435-
intercepted.
432+
intercepted. Cleanup actions specified by finally clauses of :keyword:`try` statements
433+
are honored, and it is possible to intercept the exit attempt at an outer level.
436434

437435
.. versionchanged:: 3.6
438436
If an error occurs in the cleanup after the Python interpreter

0 commit comments

Comments
 (0)