Message114183
| 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. |
|