[Python-Dev] PEP 467: Minor API improvements for bytes & bytearray (original) (raw)

Nick Coghlan ncoghlan at gmail.com
Mon Aug 18 01:51:40 CEST 2014

On 18 Aug 2014 09:41, "Raymond Hettinger" <raymond.hettinger at gmail.com> wrote:

I encourage restraint against adding an unneeded class method that has no parallel elsewhere. Right now, the learning curve is mitigated because bytes is very str-like and because bytearray is list-like (i.e. the method names have been used elsewhere and likely already learned before encountering bytes() or bytearray()). Putting in new, rarely used funky method adds to the learning burden. If you do press forward with adding it (and I don't see why), then as an alternate constructor, the name should be fromint() or some such to avoid ambiguity and to make clear that it is a class method.

If I remember the sequence of events correctly, I thought of map(bytes.byte, data) first, and then Guido suggested a dedicated iterbytes() method later.

The step I hadn't taken (until now) was realising that the new memoryview(data).iterbytes() capability actually combines with the existing (bytes([b]) for b in data) to make the original bytes.byte idea unnecessary.

Cheers, Nick. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140818/529ee30b/attachment.html>

More information about the Python-Dev mailing list