New issue 1778: PyGILState_Ensure should not deadlock if GIL already held
https://bitbucket.org/pypy/pypy/issue/1778/pygilstate_ensure-should-not-deadlock-if
Nick Williams:
PyGILState_Ensure is documented as "(ensuring) that the current thread is ready
to call the Python C API regardless of the
Armin,
> The documentation of PyGILState_Ensure() says, indeed, that it's ok to
> call this function even if the current thread already owns the GIL.
> If PyPy's version deadlocks in this case, then it's a bug of PyPy.
> Please file it as a bug (https://bitbucket.org/pypy/pypy/issues; also
> look
New issue 1777: Unable to create proper numpy array from cffi buffer
https://bitbucket.org/pypy/pypy/issue/1777/unable-to-create-proper-numpy-array-from
Yichao Yu:
I am writing something that need to convert a c buffer from cffi to a numpy
array with arbitrary shape and strides. Besides the fact
Hi Nick,
On 22 May 2014 11:23, Nick Williams wrote:
> The problem is induced when the C++ code in the module (having been invoked
> from a Python thread) prepares to call back into Python again by calling
> PyGILState_Ensure.
The documentation of PyGILState_Ensure() says, indeed, that it's ok
