This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients jcon, kermode, mark.dickinson, ncoghlan, pitrou, pv, rupole, skrah, teoliphant
Date 2011-06-26.12:35:46
SpamBayes Score 1.5958445e-05
Marked as misclassified No
Message-id <1309091747.53.0.929388930196.issue10181@psf.upfronthosting.co.za>
In-reply-to
Content
I should also note that if memoryview ends up growing enough state to cope correctly with numpy-style multi-dimensional slicing, I'm actually OK with that. You could get a long way just using the array module to allocate a large chunk of memory and then a suitably enhanced memoryview to manipulate it as a multidimensional array.

That's a future concern, though - for now, the key task is to migrate to reliable, reference based semantics for Py_buffer management.
History
Date User Action Args
2011-06-26 12:35:47ncoghlansetrecipients: + ncoghlan, teoliphant, mark.dickinson, rupole, kermode, pitrou, pv, skrah, jcon
2011-06-26 12:35:47ncoghlansetmessageid: <1309091747.53.0.929388930196.issue10181@psf.upfronthosting.co.za>
2011-06-26 12:35:47ncoghlanlinkissue10181 messages
2011-06-26 12:35:46ncoghlancreate