mirror of
https://github.com/python/cpython.git
synced 2025-08-04 00:48:58 +00:00
[3.13] gh-125058: update _thread
docs regarding interruptibility of lock.acquire()
(GH-125141) (#125306)
gh-125058: update `_thread` docs regarding interruptibility of `lock.acquire()` (GH-125141)
(cherry picked from commit 0135848059
)
Co-authored-by: Jan Kaliszewski <zuo@kaliszewski.net>
This commit is contained in:
parent
1fe27103e0
commit
49f171d9ea
1 changed files with 5 additions and 3 deletions
|
@ -219,9 +219,11 @@ In addition to these methods, lock objects can also be used via the
|
|||
* Calling :func:`sys.exit` or raising the :exc:`SystemExit` exception is
|
||||
equivalent to calling :func:`_thread.exit`.
|
||||
|
||||
* It is not possible to interrupt the :meth:`~threading.Lock.acquire` method on
|
||||
a lock --- the :exc:`KeyboardInterrupt` exception will happen after the lock
|
||||
has been acquired.
|
||||
* It is platform-dependent whether the :meth:`~threading.Lock.acquire` method
|
||||
on a lock can be interrupted (so that the :exc:`KeyboardInterrupt` exception
|
||||
will happen immediately, rather than only after the lock has been acquired or
|
||||
the operation has timed out). It can be interrupted on POSIX, but not on
|
||||
Windows.
|
||||
|
||||
* When the main thread exits, it is system defined whether the other threads
|
||||
survive. On most systems, they are killed without executing
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue