mirror of https://github.com/python/cpython
gh-125025: `_thread` docs: fix/update the *caveats* list (GH-125026)
This commit is contained in:
parent
feca4cf64e
commit
1e098dc766
|
@ -213,9 +213,8 @@ In addition to these methods, lock objects can also be used via the
|
||||||
|
|
||||||
.. index:: pair: module; signal
|
.. index:: pair: module; signal
|
||||||
|
|
||||||
* Threads interact strangely with interrupts: the :exc:`KeyboardInterrupt`
|
* Interrupts always go to the main thread (the :exc:`KeyboardInterrupt`
|
||||||
exception will be received by an arbitrary thread. (When the :mod:`signal`
|
exception will be received by that thread.)
|
||||||
module is available, interrupts always go to the main thread.)
|
|
||||||
|
|
||||||
* Calling :func:`sys.exit` or raising the :exc:`SystemExit` exception is
|
* Calling :func:`sys.exit` or raising the :exc:`SystemExit` exception is
|
||||||
equivalent to calling :func:`_thread.exit`.
|
equivalent to calling :func:`_thread.exit`.
|
||||||
|
@ -229,7 +228,3 @@ In addition to these methods, lock objects can also be used via the
|
||||||
:keyword:`try` ... :keyword:`finally` clauses or executing object
|
:keyword:`try` ... :keyword:`finally` clauses or executing object
|
||||||
destructors.
|
destructors.
|
||||||
|
|
||||||
* When the main thread exits, it does not do any of its usual cleanup (except
|
|
||||||
that :keyword:`try` ... :keyword:`finally` clauses are honored), and the
|
|
||||||
standard I/O files are not flushed.
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue