mirror of
https://github.com/python/cpython.git
synced 2025-08-03 08:34:29 +00:00
Doc nits for bpo-16500 (#1841)
* Doc nits for bpo-16500 * Fix more references
This commit is contained in:
parent
eca7da0f13
commit
f7ecfac0c1
8 changed files with 25 additions and 13 deletions
|
@ -564,7 +564,7 @@ Additionally, when extending or embedding Python, calling :c:func:`fork`
|
|||
directly rather than through :func:`os.fork` (and returning to or calling
|
||||
into Python) may result in a deadlock by one of Python's internal locks
|
||||
being held by a thread that is defunct after the fork.
|
||||
:c:func:`PyOS_AfterFork` tries to reset the necessary locks, but is not
|
||||
:c:func:`PyOS_AfterFork_Child` tries to reset the necessary locks, but is not
|
||||
always able to.
|
||||
|
||||
|
||||
|
@ -675,9 +675,9 @@ code, or when embedding the Python interpreter:
|
|||
|
||||
.. c:function:: void PyEval_ReInitThreads()
|
||||
|
||||
This function is called from :c:func:`PyOS_AfterFork` to ensure that newly
|
||||
created child processes don't hold locks referring to threads which
|
||||
are not running in the child process.
|
||||
This function is called from :c:func:`PyOS_AfterFork_Child` to ensure
|
||||
that newly created child processes don't hold locks referring to threads
|
||||
which are not running in the child process.
|
||||
|
||||
|
||||
The following functions use thread-local storage, and are not compatible
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue