Searched refs:PyOS_AfterFork_Child (Results 1 – 18 of 18) sorted by relevance
12 PyAPI_FUNC(void) PyOS_AfterFork_Child(void);
62 .. c:function:: void PyOS_AfterFork_Child()74 true for ``PyOS_AfterFork_Child()``.81 :c:func:`PyOS_AfterFork_Parent` and :c:func:`PyOS_AfterFork_Child`.92 This function is superseded by :c:func:`PyOS_AfterFork_Child()`.
880 :c:func:`PyOS_AfterFork_Child` tries to reset the necessary locks, but is not
811 PyOS_AfterFork_Child(); in do_fork_exec()
590 PyOS_AfterFork_Child(void) in PyOS_AfterFork_Child() function657 PyOS_AfterFork_Child(); in PyOS_AfterFork()6796 PyOS_AfterFork_Child(); in os_fork1_impl()6835 PyOS_AfterFork_Child(); in os_fork_impl()7505 PyOS_AfterFork_Child(); in os_forkpty_impl()
457 function,PyOS_AfterFork_Child,3.7,on platforms with fork(),
1562 PyOS_AfterFork_Child:void:::
481 …<elf-symbol name='PyOS_AfterFork_Child' type='func-type' binding='global-binding' visibility='defa…16424 …PyOS_AfterFork_Child' mangled-name='PyOS_AfterFork_Child' filepath='./Modules/posixmodule.c' line=…
2088 [function.PyOS_AfterFork_Child]
2051 It should not be called explicitly: use :c:func:`PyOS_AfterFork_Child`
6315 PyOS_AfterFork_Parent() and PyOS_AfterFork_Child().
1696 :c:func:`PyOS_AfterFork_Child`. (Contributed by Antoine Pitrou in2097 :c:func:`PyOS_AfterFork_Parent` or :c:func:`PyOS_AfterFork_Child()` instead.
2022 It should not be called explicitly: use :c:func:`PyOS_AfterFork_Child`
4151 :c:func:`PyOS_AfterFork_Parent` and :c:func:`PyOS_AfterFork_Child`.