2011/10/31 Stéfan van der Walt :
> On Mon, Oct 31, 2011 at 11:28 AM, Zachary Pincus
> wrote:
>>> As an example, it'd be nice to have scipy.ndimage available without the GIL:
>>> http://docs.scipy.org/doc/scipy/reference/ndimage.html
>>>
>>> Now, this *can* easily be done as the core is written in
On Mon, Oct 31, 2011 at 11:28 AM, Zachary Pincus
wrote:
>> As an example, it'd be nice to have scipy.ndimage available without the GIL:
>> http://docs.scipy.org/doc/scipy/reference/ndimage.html
>>
>> Now, this *can* easily be done as the core is written in C++. I'm just
>> pointing out that some p
> As an example, it'd be nice to have scipy.ndimage available without the GIL:
> http://docs.scipy.org/doc/scipy/reference/ndimage.html
>
> Now, this *can* easily be done as the core is written in C++. I'm just
> pointing out that some people may wish more for calling scipy.ndimage
> inside thei
On 10/31/2011 12:01 PM, Dag Sverre Seljebotn wrote:
> On 10/31/2011 11:48 AM, mark florisson wrote:
>> On 31 October 2011 10:03, Dag Sverre Seljebotn
>>wrote:
>>> Mark: I'm just wondering what you wanted to do with NumPy from Cython -- a
>>> stopgap solution for SIMD, iterator support, or somet
On 10/31/2011 11:48 AM, mark florisson wrote:
> On 31 October 2011 10:03, Dag Sverre Seljebotn
> wrote:
>> Mark: I'm just wondering what you wanted to do with NumPy from Cython -- a
>> stopgap solution for SIMD, iterator support, or something else?
>>
>> SIMD using NumPy really isn't the best ide
On 31 October 2011 09:50, Pauli Virtanen wrote:
> 31.10.2011 09:44, mark florisson kirjoitti:
> [clip]
>> Ah, that's too bad. Is it anywhere near ready, or was it abandoned for
>> ironclad? Could you point me to the code?
>
> It's quite ready and working, and as far as I understand, Enthought is
>
On 31 October 2011 10:03, Dag Sverre Seljebotn
wrote:
> Mark: I'm just wondering what you wanted to do with NumPy from Cython -- a
> stopgap solution for SIMD, iterator support, or something else?
>
> SIMD using NumPy really isn't the best idea long-term because of all the
> temporaries needed in
Mark: I'm just wondering what you wanted to do with NumPy from Cython -- a
stopgap solution for SIMD, iterator support, or something else?
SIMD using NumPy really isn't the best idea long-term because of all the
temporaries needed in compound expressions, which is really bad on the memory
bus f
31.10.2011 09:44, mark florisson kirjoitti:
[clip]
> Ah, that's too bad. Is it anywhere near ready, or was it abandoned for
> ironclad? Could you point me to the code?
It's quite ready and working, and as far as I understand, Enthought is
shipping it. I haven't used it, though.
The code is here:
On 30 October 2011 21:01, Pauli Virtanen wrote:
> 30.10.2011 21:48, mark florisson kirjoitti:
>> First, I'd like to report a bug. It seems ndarray does not implement
>> tp_traverse or tp_clear, so if you have a reference cycle in an
>> ndarray with dtype object none of those objects will ever be
>
30.10.2011 21:48, mark florisson kirjoitti:
> First, I'd like to report a bug. It seems ndarray does not implement
> tp_traverse or tp_clear, so if you have a reference cycle in an
> ndarray with dtype object none of those objects will ever be
> collected.
Indeed, this is missing. http://projects.
Hello,
First, I'd like to report a bug. It seems ndarray does not implement
tp_traverse or tp_clear, so if you have a reference cycle in an
ndarray with dtype object none of those objects will ever be
collected.
Secondly, please bear with me, I'm not a NumPy expert, but would it be
possible to ha
12 matches
Mail list logo