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 christian.heimes, docs@python, ebianchi, ezio.melotti, martin.panter, pitrou, r.david.murray
Date 2016-09-09.01:34:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473384840.85.0.0724394081399.issue20762@psf.upfronthosting.co.za>
In-reply-to
Content
In the meantime, full documentation for the read() and write() methods was added for Python 3 in revision 61e52fda1006. The Python 2 documentation only mentions read() indirectly, in passing and in example code, and does not mention write().

But deprecating them makes sense to me. The essential functionality seems to already be available in the recv(), recv_into(), and send() or sendall() methods. The write() documentation is not clear regarding partial writes, in constrast with send() and sendall().
History
Date User Action Args
2016-09-09 01:34:00martin.pantersetrecipients: + martin.panter, pitrou, christian.heimes, ezio.melotti, r.david.murray, docs@python, ebianchi
2016-09-09 01:34:00martin.pantersetmessageid: <1473384840.85.0.0724394081399.issue20762@psf.upfronthosting.co.za>
2016-09-09 01:34:00martin.panterlinkissue20762 messages
2016-09-09 01:34:00martin.pantercreate