Message168818
> Those macros only work for general GIL releasing and pop straight
> away, not for the case where released, calls into some non Python C
> library, which then calls back into Python.
I see, so you are right that this new API could be useful. However, we
should also add a new GIL state API that fixes the issue for good (by
passing an interpreter), otherwise we will still have such discussions
in five years and it will be very silly.
> My recollection is, and so unless they have changed it, SWIG generated
> calls use the GILState calls. See:
Well, if SWIG isn't fixed, people should stop using an unmaintained and
buggy tool. |
|
Date |
User |
Action |
Args |
2012-08-21 22:56:45 | pitrou | set | recipients:
+ pitrou, ncoghlan, grahamd |
2012-08-21 22:56:45 | pitrou | link | issue15751 messages |
2012-08-21 22:56:44 | pitrou | create | |
|