From: Ezio Melotti Date: Wed, 20 Apr 2011 18:29:31 +0000 (+0300) Subject: Fix wrong function name. Noticed by Clive Darke. X-Git-Tag: v3.2.1b1~98^2 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e4027249127ad7150892d528978b2862a78c6284;p=python Fix wrong function name. Noticed by Clive Darke. --- diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst index 12abf1e9e6..e78add1041 100644 --- a/Doc/c-api/init.rst +++ b/Doc/c-api/init.rst @@ -472,7 +472,7 @@ the fork, and releasing them afterwards. In addition, it resets any :ref:`lock-objects` in the child. When extending or embedding Python, there is no way to inform Python of additional (non-Python) locks that need to be acquired before or reset after a fork. OS facilities such as -:cfunc:`posix_atfork` would need to be used to accomplish the same thing. +:cfunc:`pthread_atfork` would need to be used to accomplish the same thing. Additionally, when extending or embedding Python, calling :cfunc:`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