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 ezio.melotti
Recipients chris.jerdonek, docs@python, eric.araujo, ezio.melotti, pitrou, terry.reedy
Date 2012-11-23.20:30:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353702644.92.0.989432698637.issue16518@psf.upfronthosting.co.za>
In-reply-to
Content
> "Buffer object" doesn't mean anything in Python 3 and, furthermore,
> it might be mixed up with the Python 2 `buffer` type.

Agreed.

> As for the error messages, they are generally very bad on this topic,
> so I would vote to change them :-)

I would say that they are verbose maybe, but not necessary bad.
Using "any object that supports the buffer protocol" without explicitly mentioning bytes (and bytearray) might end up being even more confusing (if that's what it's being proposed).
History
Date User Action Args
2012-11-23 20:30:44ezio.melottisetrecipients: + ezio.melotti, terry.reedy, pitrou, eric.araujo, chris.jerdonek, docs@python
2012-11-23 20:30:44ezio.melottisetmessageid: <1353702644.92.0.989432698637.issue16518@psf.upfronthosting.co.za>
2012-11-23 20:30:44ezio.melottilinkissue16518 messages
2012-11-23 20:30:44ezio.melotticreate