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 chris.jerdonek
Recipients Guillaume.Bouchard, chris.jerdonek, docs@python, eric.araujo, ezio.melotti, pitrou, r.david.murray, terry.reedy
Date 2012-10-16.07:11:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1350371467.23.0.174864849643.issue13538@psf.upfronthosting.co.za>
In-reply-to
Content
Attaching updated patch based on Ezio and Antoine's comments.  Let me know if I'm not using the correct or preferred terminology around buffer objects and the buffer protocol.

It doesn't seem like the section on the buffer protocol actually says what objects implementing the buffer protocol should be called.  I gather indirectly from the docs that such objects are called "buffer objects" (as opposed to just "buffers"):

http://docs.python.org/dev/c-api/buffer.html#bufferobjects
History
Date User Action Args
2012-10-16 07:11:08chris.jerdoneksetrecipients: + chris.jerdonek, terry.reedy, pitrou, ezio.melotti, eric.araujo, r.david.murray, docs@python, Guillaume.Bouchard
2012-10-16 07:11:07chris.jerdoneksetmessageid: <1350371467.23.0.174864849643.issue13538@psf.upfronthosting.co.za>
2012-10-16 07:11:07chris.jerdoneklinkissue13538 messages
2012-10-16 07:11:06chris.jerdonekcreate