> Some parts of the numpy code release the GIL, so it needs to be reacquired
> in order to call the Python C_API. A quick look shows a call to
> PyObject_Print in the function and there may be other such calls. The right
> fix is probably to use a couple of ifdefs if there is an easy way to
> deter
On Tue, Aug 14, 2012 at 3:13 PM, Charles R Harris
wrote:
>
>
> On Tue, Aug 14, 2012 at 7:47 AM, Aron Ahmadia wrote:
>>
>> Hi all,
>>
>> Installing numpy 1.6.2 against a Python interpreter built with the
>> --without threads currently fails due to missing references to
>> PyGILState_Ensure and PyG
On Tue, Aug 14, 2012 at 7:47 AM, Aron Ahmadia wrote:
> Hi all,
>
> Installing numpy 1.6.2 against a Python interpreter built with the
> --without threads currently fails due to missing references
> to PyGILState_Ensure and PyGILState_Release. The references appear to be
> coming from the followi
Hi all,
Installing numpy 1.6.2 against a Python interpreter built with the
--without threads currently fails due to missing references
to PyGILState_Ensure and PyGILState_Release. The references appear to be
coming from the following code in nditer.c.src:
NPY_NO_EXPORT void
NpyIter_DebugPrint(Np
