From e4027249127ad7150892d528978b2862a78c6284 Mon Sep 17 00:00:00 2001 From: Ezio Melotti Date: Wed, 20 Apr 2011 21:29:31 +0300 Subject: [PATCH] Fix wrong function name. Noticed by Clive Darke. --- Doc/c-api/init.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst index 12abf1e9e6b..e78add1041a 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