[3.8] closes bpo-32165: Fix calling order of PyEval_InitThreads. (GH-4602) #15836
Conversation
As described in Doc/c-api/init.rst, PyEval_InitThreads() cannot be called before Py_Initialize() function. (cherry picked from commit 9e61066) Co-authored-by: Kenta Murata <[email protected]>
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Our records indicate we have not received your CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for your contribution, we look forward to reviewing it! |
benjaminp
changed the title
|
@mrkn and @benjaminp: Status check is done, and it's a success ✅ . |
2 similar comments
|
@mrkn and @benjaminp: Status check is done, and it's a success ✅ . |
|
@mrkn and @benjaminp: Status check is done, and it's a success ✅ . |
5 participants
As described in Doc/c-api/init.rst, PyEval_InitThreads() cannot be called
before Py_Initialize() function.
(cherry picked from commit 9e61066)
Co-authored-by: Kenta Murata [email protected]
https://bugs.python.org/issue32165