On 06.10.14 00:24, Greg Ewing wrote: > anatoly techtonik wrote: >> That's a cool stuff. `bytes-like object` is really a much better name >> for users. > > I'm not so sure. Usually when we talk about an "xxx-like object" we > mean one that supports a certain Python interface, e.g. a "file-like > object" is one that has read() and/or write() methods. But you can't > create an object that supports the buffer protocol by implementing > Python methods. > > I'm worried that using the term "bytes-like object" will lead > people to ask "What methods do I have to implement to make my > object bytes-like?", to which the answer is "mu". Other (rarely used) alternatives are "buffer-like object" and "buffer-compatible object".
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4