Skip to content

Commit 9d9dc59

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

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
@@ -429,10 +429,7 @@ always available.
429429

430430
.. function:: exit([arg])
431431

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

437434
The optional argument *arg* can be an integer giving the exit status
438435
(defaulting to zero), or another type of object. If it is an integer, zero
@@ -449,7 +446,8 @@ always available.
449446

450447
Since :func:`exit` ultimately "only" raises an exception, it will only exit
451448
the process when called from the main thread, and the exception is not
452-
intercepted.
449+
intercepted. Cleanup actions specified by finally clauses of :keyword:`try` statements
450+
are honored, and it is possible to intercept the exit attempt at an outer level.
453451

454452
.. versionchanged:: 3.6
455453
If an error occurs in the cleanup after the Python interpreter

0 commit comments

Comments
 (0)