[Python-Dev] Why does read() return bytes instead of bytearray? (original) (raw)
Benjamin Peterson benjamin at python.org
Wed Apr 15 22:37:47 CEST 2009
- Previous message: [Python-Dev] Why does read() return bytes instead of bytearray?
- Next message: [Python-Dev] Why does read() return bytes instead of bytearray?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2009/4/15 R. David Murray <rdmurray at bitdance.com>:
On Tue, 14 Apr 2009 at 22:05, Dan Eloff wrote:
No, the read() method did not change from the 2.x series. It returns a new object on each call. I think you misunderstand me, but the readinto() method looks like a perfectly reasonable solution, I didn't realize it existed, as it's not in the library reference on file objects. Thanks for enlightening me, I feel a little stupid now :) You have to follow the link from that section to the 'io' module to find it. The io module is about streams and is therefore in the 'generic operating system services' section, not the 'file and directory access section', which makes it a little harder to find when what you think you want to know about is file access...I think this is a doc bug but I'm completely unsure what would be a good fix.
I've added a like to the io module in the see also section of the file and directory systems.
-- Regards, Benjamin
- Previous message: [Python-Dev] Why does read() return bytes instead of bytearray?
- Next message: [Python-Dev] Why does read() return bytes instead of bytearray?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]