summaryrefslogtreecommitdiffstats
path: root/Doc/c-api
diff options
context:
space:
mode:
authorEzio Melotti <ezio.melotti@gmail.com>2011-04-20 18:29:31 (GMT)
committerEzio Melotti <ezio.melotti@gmail.com>2011-04-20 18:29:31 (GMT)
commite4027249127ad7150892d528978b2862a78c6284 (patch)
tree3f6eb7bc5f304fe87b7c70741f59cb9f2629c6ac /Doc/c-api
parentac4515063c18157645d135bca8c4cf39542ccd6e (diff)
downloadcpython-e4027249127ad7150892d528978b2862a78c6284.zip
cpython-e4027249127ad7150892d528978b2862a78c6284.tar.gz
cpython-e4027249127ad7150892d528978b2862a78c6284.tar.bz2
Fix wrong function name. Noticed by Clive Darke.
Diffstat (limited to 'Doc/c-api')
-rw-r--r--Doc/c-api/init.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst
index 12abf1e..e78add1 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