On Fri, May 11, 2012 at 09:59:16AM -0500, Travis Oliphant wrote:
> > Is there a advantage for users by making it a subclass? Nobody is saying
> > you couldn't 'inherit' the struct (make the ndmask struct be castable to
> > a PyArrayObject*) even if that is not declared in the Python type object.
On 05/11/2012 01:36 AM, Travis Oliphant wrote:
>>>
>>> I guess this mixture of Python-API and C-API is different from the way
>>> the API tries to protect incorrect access. From the Python API, it.
>>> should let everything through, because it's for Python code to use. From
>>> the C API, it should
>>
>> See my post in the other thread for my proposal to add a flag that allows
>> users to switch between the Python side default being ndarray's or ndmasked,
>> but they are different types at the C-level.The proposal so far does not
>> specify whether or not ndarray or ndmasked is a subc
On 05/11/2012 07:36 AM, Travis Oliphant wrote:
>>>
>>> I guess this mixture of Python-API and C-API is different from the way
>>> the API tries to protect incorrect access. From the Python API, it.
>>> should let everything through, because it's for Python code to use. From
>>> the C API, it should
>>
>> I guess this mixture of Python-API and C-API is different from the way
>> the API tries to protect incorrect access. From the Python API, it.
>> should let everything through, because it's for Python code to use. From
>> the C API, it should default to not letting things through, because
>>
Dag Sverre Seljebotn wrote:
>On 05/11/2012 01:06 AM, Mark Wiebe wrote:
>> On Thu, May 10, 2012 at 5:47 PM, Dag Sverre Seljebotn
>> mailto:d.s.seljeb...@astro.uio.no>>
>wrote:
>>
>> On 05/11/2012 12:28 AM, Mark Wiebe wrote:
>> > I did some searching for typical Cython and C code which
>
Dag Sverre Seljebotn wrote:
>On 05/11/2012 01:06 AM, Mark Wiebe wrote:
>> On Thu, May 10, 2012 at 5:47 PM, Dag Sverre Seljebotn
>> mailto:d.s.seljeb...@astro.uio.no>>
>wrote:
>>
>> On 05/11/2012 12:28 AM, Mark Wiebe wrote:
>> > I did some searching for typical Cython and C code which
>
On 05/11/2012 01:06 AM, Mark Wiebe wrote:
> On Thu, May 10, 2012 at 5:47 PM, Dag Sverre Seljebotn
> mailto:d.s.seljeb...@astro.uio.no>> wrote:
>
> On 05/11/2012 12:28 AM, Mark Wiebe wrote:
> > I did some searching for typical Cython and C code which accesses
> numpy
> > arrays, an
On Thu, May 10, 2012 at 5:47 PM, Dag Sverre Seljebotn <
d.s.seljeb...@astro.uio.no> wrote:
> On 05/11/2012 12:28 AM, Mark Wiebe wrote:
> > I did some searching for typical Cython and C code which accesses numpy
> > arrays, and added a section to the NEP describing how they behave in the
> > curren
On 05/11/2012 12:47 AM, Dag Sverre Seljebotn wrote:
> On 05/11/2012 12:28 AM, Mark Wiebe wrote:
>> I did some searching for typical Cython and C code which accesses numpy
>> arrays, and added a section to the NEP describing how they behave in the
>> current implementation. Cython code which uses ei
On 05/11/2012 12:28 AM, Mark Wiebe wrote:
> I did some searching for typical Cython and C code which accesses numpy
> arrays, and added a section to the NEP describing how they behave in the
> current implementation. Cython code which uses either straight Python
> access or the buffer protocol is f
I did some searching for typical Cython and C code which accesses numpy
arrays, and added a section to the NEP describing how they behave in the
current implementation. Cython code which uses either straight Python
access or the buffer protocol is fine (after a bugfix in numpy, it wasn't
failing cu
12 matches
Mail list logo
