Andrew Svetlov <andrew.svet...@gmail.com> added the comment:
Exposing internal buffer means committing on a new API contract forever. I feel a need for reacher read*() API but pretty sure that making internal buffer public is a bad idea. With BufferedProtocol it could be even worse: SLAB allocators can spit a buffer into several separate chunks. `str.startswith()` supports a tuple of separators, maybe we can do the same for streaming API ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32052> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
