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 skrah
Recipients chris.jerdonek, docs@python, eric.araujo, ezio.melotti, pitrou, skrah, terry.reedy
Date 2012-11-23.21:54:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <1353704267.3343.3.camel@localhost.localdomain>
Antoine Pitrou <> wrote:
> > 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.

Ok, but people should not be surprised if their (Python) array.array() of
double or their array of ctypes structs is silently accepted by some byte
consuming function.

How about "object does not provide a byte buffer" for error messages
and "(byte) buffer provider" as a shorthand for "any buffer provider
that exposes its memory as a sequence of unsigned bytes in response
to a PyBUF_SIMPLE request"?
Date User Action Args
2012-11-23 21:54:13skrahsetrecipients: + skrah, terry.reedy, pitrou, ezio.melotti, eric.araujo, chris.jerdonek, docs@python
2012-11-23 21:54:13skrahlinkissue16518 messages
2012-11-23 21:54:13skrahcreate