On 10/06/2014 06:34 AM, Nick Coghlan wrote: > 3. "buffer" is a completely new term for most users, and one that > refers to an implementation detail of memoryview, moreso than > something developers actually need to care about. Using it directly in > error messages and documentation is to make the abstraction leak in a > way that raises unnecessary barriers to entry. Especially since buffer() is gone in Py3. The only prominent mention of "buffer" in the docs is now the C API section that explains the buffer protocol. Since this is cross-referenced from the "bytes-like object" glossary, it will lead people who want to write such an object to the right place. Georg
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