This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients martin.panter, mbussonn, serhiy.storchaka, takluyver
Date 2016-01-29.01:48:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I left some review comments.

Since the rules for read-only and write-only access are so different, would it make more sense to have a separate method? Maybe your writefile() name, or open_write() or something? I am not too fussed, but unless there is a chance of being able to open a read-write random access file, I find these split-personality open() methods a bit “un-Pythonic”. On the other hand, I guess it is superficially consistent with other open() functions.

Also, perhaps if you guaranteed the write-only option returned a file-like object, you could use shutil.copyfileobj() rather than a custom read-write loop.
Date User Action Args
2016-01-29 01:48:07martin.pantersetrecipients: + martin.panter, takluyver, serhiy.storchaka, mbussonn
2016-01-29 01:48:07martin.pantersetmessageid: <>
2016-01-29 01:48:07martin.panterlinkissue26039 messages
2016-01-29 01:48:06martin.pantercreate