[Numpy-discussion] Porting strategy for py3k

David Cournapeau cournape@gmail....
Sun May 3 23:03:37 CDT 2009


On Mon, May 4, 2009 at 1:24 AM, Dag Sverre Seljebotn
<dagss@student.matnat.uio.no> wrote:
> David Cournapeau wrote:
>> On Fri, Apr 24, 2009 at 4:49 PM, Dag Sverre Seljebotn
>>> One thing somebody *could* work on rather independently for some hours
>>> is proper PEP 3118 support, as that is available in Python 2.6+ as well
>>> and could be conditionally used on those systems.
>>
>> Yes, this could be done independently. I am not familiar with PEP
>> 3118; from the python-dev ML, it looks like the current buffer API has
>> some serious shortcomings, I don't whether this implies to numpy or
>> not. Do you have more on this ?
>
> Not sure what you refer to ...

http://mail.python.org/pipermail/python-dev/2009-April/088211.html

Thank you for those information.

I don't understand what is meant by "not implemented for
multi-dimensional array", and the consequences for numpy. Does it mean
that PEP 3118 is not fully implemented ? Is the status of the buffer
interface the same for python 2.6 and python 3 ?

> In addition it would be natural to act as a client, so that calling
> "np.array(obj)" (and/or np.view?) would acquire the data through PEP 3118.

Yes, it would help making sure we implement the interface correctly for once :)

I am almost done having a numpy.distutils which can bootstrap itself
to the point of converting the rest of the python code to py3k. With
the buffer interface, this should enable moving forward in a piecewise
manner.

thank you,

David


More information about the Numpy-discussion mailing list