On Jan 6, 2005, at 7:22 AM, Thomas Heller wrote: > (*) Which brings me to the questions I have in my mind for quite some > time: Why is readinto undocumented, and what about the status of the > buffer object: do the recent fixes to the buffer object change it's > status? I, for one, would be very unhappy if the byte buffer object were to go away. It's quite useful. I didn't even realize readinto existed. It'd be great to add more of them. os.readinto for reading from fds and socket.socket.recvinto for reading from sockets. Is there any reason the writable buffer interface isn't exposed to python-land? James
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