➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: PyEval_InitThreads is called before Py_Initialize in LoadPython in Modules/_ctypes/callbacks.c
Type: Stage: resolved
Components: ctypes Versions: Python 3.6
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: amaury.forgeotdarc, belopolsky, meador.inge, mrkn
Priority: normal Keywords: patch

Created on 2017-11-29 02:56 by mrkn, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 4602 merged mrkn, 2017-11-29 02:56
PR 15832 closed miss-islington, 2019-09-10 10:30
PR 15833 merged miss-islington, 2019-09-10 10:31
PR 15836 merged miss-islington, 2019-09-10 11:11
Messages (1)
msg307202 - (view) Author: Kenta Murata (mrkn) Date: 2017-11-29 02:56 
As described in Doc/c-api/init.rst, PyEval_InitThreads() cannot be called
before Py_Initialize() function.
But in Modules/_ctypes/callbacks.c, PyEval_InitThreds() is called before Py_Initialize() in LoadPython function.
History
Date User Action Args
2022-04-11 14:58:55adminsetgithub: 76346
2019-09-10 14:38:50benjamin.petersonsetstatus: open -> closed
resolution: fixed
stage: patch review -> resolved
2019-09-10 11:11:18miss-islingtonsetpull_requests: + pull_request15481
2019-09-10 10:31:08miss-islingtonsetpull_requests: + pull_request15478
2019-09-10 10:30:38miss-islingtonsetkeywords: + patch
pull_requests: + pull_request15477
2018-03-10 18:41:45ned.deilysetnosy: + amaury.forgeotdarc, belopolsky, meador.inge

stage: patch review
2017-11-29 02:56:08mrkncreate