bpo-16500: Allow registering at-fork handlers#1715
Conversation
|
@pitrou, thanks for your PR! By analyzing the history of the files in this pull request, we identified @serhiy-storchaka, @rhettinger and @tim-one to be potential reviewers. |
Sorry, something went wrong.
Yes, LGTM from me. I'm going to use this API in uvloop (now I use |
Sorry, something went wrong.
|
My only question (that shouldn't block this PR from being merged) is can we use |
Sorry, something went wrong.
|
If fork() was called without the GIL had, the child process interpreter
could be in an unrecoverable non reentrant state.
…On Fri, May 26, 2017, 1:17 PM Yury Selivanov ***@***.***> wrote:
My only question (that shouldn't block this PR from being merged) is can
we use pthread_atfork in CPython? That would make this API work even when
a C extension is calling fork directly, bypassing the CPython API.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1715 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAELiymvfCsEjaXBQThXDfFlUB4sfiwkks5r9zNjgaJpZM4NiROU>
.
|
Sorry, something went wrong.
|
Thanks, Gregory, it makes sense. |
Sorry, something went wrong.
Resolve conflicts: 346cbd3 bpo-16500: Allow registering at-fork handlers (python#1715)
No description provided.