[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

STINNER Victor added the comment: Commited as r84163 to 3.2. Don't backport because it is not really a bug and I prefer to avoid touching stable branches with such minor details. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

Changes by STINNER Victor : -- resolution: fixed -> status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

Changes by STINNER Victor : Removed file: http://bugs.python.org/file16439/gil_state_init-trunk.patch ___ Python tracker ___ ___ Python-bugs-li

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

STINNER Victor added the comment: While working on #9425, I usually hit two annoying issues: - _PyObject_Dump() crashs (assertion error) if I call it (with gdb) in Py_InitializeEx() - because of python-gdb.py, gdb does segfault (I don't know yet where it does come from) So I'm back on the G

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

STINNER Victor added the comment: My SIGINT.patch for #3137 moves the call to _PyGILState_Init() just before initsite(), so it doesn't change too much Py_InitializeEx() and it's enough for me :-) -- ___ Python tracker

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

STINNER Victor added the comment: I found the following issue in Roundup tracker to restore a deleted message: http://psf.upfronthosting.co.za/roundup/meta/issue267 I tried to write the URL, but it doesn't work: http://bugs.python.org/issue80...@action=edit&@a...@messages=100432 I tried also u

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

STINNER Victor added the comment: > haypo, it seems you removed the initial message... I know... My mouse clicked on [remove] button, it wasn't me! I don't know how to restore it. The message: msg100432. -- ___ Python tracker

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

Amaury Forgeot d'Arc added the comment: haypo, it seems you removed the initial message... -- ___ Python tracker ___ ___ Python-bugs-l

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

Changes by STINNER Victor : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/op

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

Amaury Forgeot d'Arc added the comment: I would keep the call to PyThreadState_Swap() next to PyThreadState_New(): create the thread state and install it. _PyGILState_Init() may come after. -- nosy: +amaury.forgeotdarc ___ Python tracker

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

STINNER Victor added the comment: See also #3137. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

STINNER Victor added the comment: haypo> I already hitted this bug some weeks ago when I was working haypo> on the thread state preallocation when creating a new thread: haypo> #7544. According to msg97715: it was indirectly the same issue, call _PyObject_Dump() while the GIL is not initializ

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

New submission from STINNER Victor : _PyGILState_Init() initialize autoInterpreterState variable. This variable have to be set before the first call to PyGILState_Ensure(). The problem is that _PyGILState_Init() is called late: at the end of Py_InitializeEx(). It's called after initsite(), whe