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 v+python
Recipients amaury.forgeotdarc, brian.curtin, gvanrossum, pebbe, pitrou, v+python
Date 2011-01-06.11:15:55
SpamBayes Score 0.033967283
Marked as misclassified No
Message-id <>
Makes sense to me.  Still should document the open file parameter when passed an fd, and either tell the user that it should be O_BINARY, or that it will be O_BINARYd for them, whichever technique is chosen.  But having two newline techniques is bad, and if Python thinks it is tracking the file pointer, but Windows is doing newline translation for it, then it isn't likely tracking it correctly for random access IO.  So I think the choice should be that any fd passed in to open on Windows should get O_BINARYd immediately.
Date User Action Args
2011-01-06 11:15:57v+pythonsetrecipients: + v+python, gvanrossum, amaury.forgeotdarc, pitrou, brian.curtin, pebbe
2011-01-06 11:15:57v+pythonsetmessageid: <>
2011-01-06 11:15:55v+pythonlinkissue10841 messages
2011-01-06 11:15:55v+pythoncreate