On 02/29/2012 09:42 AM, Stefan Behnel wrote:
Dag Sverre Seljebotn, 29.02.2012 18:06:
I'm wondering what the best course of action for deprecating the shape
field in numpy.pxd is.
The thing is, currently "shape" really gets in the way. In most situations
it is OK with slow access to shape throug
Dag Sverre Seljebotn, 29.02.2012 18:06:
> I'm wondering what the best course of action for deprecating the shape
> field in numpy.pxd is.
>
> The thing is, currently "shape" really gets in the way. In most situations
> it is OK with slow access to shape through the Python layer, and
> "arr.shape[0
I'm wondering what the best course of action for deprecating the shape
field in numpy.pxd is.
The thing is, currently "shape" really gets in the way. In most
situations it is OK with slow access to shape through the Python layer,
and "arr.shape[0]" is often just fine, but currently one is in a
Stefan Behnel, 29.02.2012 14:42:
> Stefan Behnel, 29.02.2012 14:34:
>> Henry Gomersall, 29.02.2012 14:30:
>>> What's the preferred way to clean up a C library when a module is
>>> deleted?
>>
>> PEP 3121:
>>
>> http://www.python.org/dev/peps/pep-3121/
>>
>> However, given that CPython doesn't curre