You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee=Noneclosed_at=<Date2019-05-13.10:35:55.872>created_at=<Date2019-04-25.23:22:09.307>labels= ['interpreter-core', '3.8']
title='Remove PyEval_ReInitThreads() from the public C API'updated_at=<Date2019-05-13.14:22:56.780>user='https://github.com/vstinner'
Charles Waldman's patch to reinitialize the interpreter lock after a
fork. This solves the test_fork1 problem. (ceval.c, signalmodule.c,
SourceForge: [ Patch bpo-101226 ] make threading fork-safe
fwiw - i agree that this can be removed. it has no reason to ever be called directly. i double checked in our massive internal codebase at work and found no calls other than python interpreters themselves.