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: v2.7.2rc1~131 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=ffdf94ae791a3e36fd28daac9f034d8706aec819;p=thirdparty%2FPython%2Fcpython.git Fix wrong function name. Noticed by Clive Darke. --- diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst index a4e4ad9a3c60..27408a41766b 100644 --- a/Doc/c-api/init.rst +++ b/Doc/c-api/init.rst @@ -474,7 +474,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