> array.array is the only type in the core that's a read buffer but not > a character buffer, and I can't find any semantic differences between > read and character buffers. If someone can explain the differences or > confirm that there aren't any, I'll make this work. The easiest thing > to do would be to make array support the character buffer API (but > maybe only for [cbBu] types?). Ah, that makes sense. And no please, keep it that way. It's compatible with the idea that bytes arrays should be read from / written to binary files. -- --Guido van Rossum (home page: http://www.python.org/~guido/)
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