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 taleinat
Recipients docs@python, joders, taleinat, terry.reedy
Date 2018-07-25.18:11:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532542280.19.0.56676864532.issue33121@psf.upfronthosting.co.za>
In-reply-to
Content
My guess would be the docs for socket.recv()[1], which indeed don't mention what the return value is after a socket has been closed, nor can I find that info elsewhere on that page.

Those docs for socket generally avoid going into detail, including specifically regarding returned values.  Apparently the approach is that this general note about the class explains where to look for more info:

"Socket objects have the following methods. Except for makefile(), these correspond to Unix system calls applicable to sockets."

Given this, I don't think adding this one small detail would be in line with the existing approach to documenting the socket class.


..[1]: https://docs.python.org/3/library/socket.html#socket.socket.recv
History
Date User Action Args
2018-07-25 18:11:20taleinatsetrecipients: + taleinat, terry.reedy, docs@python, joders
2018-07-25 18:11:20taleinatsetmessageid: <1532542280.19.0.56676864532.issue33121@psf.upfronthosting.co.za>
2018-07-25 18:11:20taleinatlinkissue33121 messages
2018-07-25 18:11:20taleinatcreate