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 Antoon.Pardon
Recipients Antoon.Pardon
Date 2013-01-10.13:40:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357825217.2.0.655032840521.issue16915@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation of socket.makefile states that its arguments are interpreted the same way as by the built-in open() function. However the mode argument of socket.makefile only allows 'r', 'w' and 'b'.

That some options are not allowed seems perfectly normal, like there being no use of an 'x' option but the documentation should probably reflect that.

But I don't see why the 't' should cause trouble. If people can open a file explicitly in text mode, I don't see why it wouldn't be possible to explicitly ask for text mode in socket.makefile
History
Date User Action Args
2013-01-10 13:40:17Antoon.Pardonsetrecipients: + Antoon.Pardon
2013-01-10 13:40:17Antoon.Pardonsetmessageid: <1357825217.2.0.655032840521.issue16915@psf.upfronthosting.co.za>
2013-01-10 13:40:16Antoon.Pardonlinkissue16915 messages
2013-01-10 13:40:15Antoon.Pardoncreate