Message 114183 - Python tracker

➜

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.

Author	vstinner
Recipients	amaury.forgeotdarc, loewis, pitrou, tim.peters, vstinner
Date	2010-08-17.22:14:04
SpamBayes Score	1.3060243e-07
Marked as misclassified	No
Message-id	<1282083247.08.0.665891535964.issue8063@psf.upfronthosting.co.za>
In-reply-to

Content
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 GIL topic: I still would like to initialize the GIL earlier in Py_InitializeEx(). As Amaury wrote, I think that the right place is just after "(void) PyThreadState_Swap(tstate);". This is exactly what does my new patch (for py3k). I think that only python 3.2 should be patched.

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 GIL topic: I still would like to initialize the GIL earlier in Py_InitializeEx(). As Amaury wrote, I think that the right place is just after "(void) PyThreadState_Swap(tstate);". This is exactly what does my new patch (for py3k).

I think that only python 3.2 should be patched.

History
Date	User	Action	Args
2010-08-17 22:14:07	vstinner	set	recipients: + vstinner, tim.peters, loewis, amaury.forgeotdarc, pitrou
2010-08-17 22:14:07	vstinner	set	messageid: <1282083247.08.0.665891535964.issue8063@psf.upfronthosting.co.za>
2010-08-17 22:14:05	vstinner	link	issue8063 messages
2010-08-17 22:14:05	vstinner	create