Message 176252 - Python tracker

➜

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	pitrou
Recipients	chris.jerdonek, docs@python, eric.araujo, ezio.melotti, pitrou, skrah, terry.reedy
Date	2012-11-23.20:58:44
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1353704267.3343.3.camel@localhost.localdomain>
In-reply-to	<1353703765.27.0.369159029402.issue16518@psf.upfronthosting.co.za>

Content
> I wouldn't use "bytes-like object". One can certainly argue that memoryview > should be bytes-like as a matter of preference, but the buffer protocol > specifies strongly (or even statically) typed multi-dimensional arrays. Ach :-( > PEP-3118 Py_buffer structs are essentially how NumPy works internally. Well, we should still write a Python documentation, not a NumPy documentation (on this tracker anyway). Outside of NumPy, there's little use for multi-dimensional objects.

> I wouldn't use "bytes-like object". One can certainly argue that *memoryview*
> should be bytes-like as a matter of preference, but the buffer protocol
> specifies strongly (or even statically) typed multi-dimensional arrays.

Ach :-(

> PEP-3118 Py_buffer structs are essentially how NumPy works internally.

Well, we should still write a Python documentation, not a NumPy
documentation (on this tracker anyway). Outside of NumPy, there's little
use for multi-dimensional objects.

History
Date	User	Action	Args
2012-11-23 20:58:44	pitrou	set	recipients: + pitrou, terry.reedy, ezio.melotti, eric.araujo, skrah, chris.jerdonek, docs@python
2012-11-23 20:58:44	pitrou	link	issue16518 messages
2012-11-23 20:58:44	pitrou	create