[issue12126] incorrect select documentation

Eli Bendersky added the comment: Closing this issue, since it specifically refers to the select error which was fixed. Tracking the removal of the sockets howto document can be done elsewhere. -- resolution: -> fixed status: open -> closed ___ Pyth

[issue12126] incorrect select documentation

Roundup Robot added the comment: New changeset ca4d9ccb6894 by Eli Bendersky in branch '3.1': Issue 12126: removing incorrect claim about return value of select http://hg.python.org/cpython/rev/ca4d9ccb6894 New changeset c26d551b5ff6 by Eli Bendersky in branch '3.2': Issue 12126: removing incor

[issue12126] incorrect select documentation

Roundup Robot added the comment: New changeset c0a3e17e677f by Eli Bendersky in branch '2.7': Issue 12126: removing incorrect claim about return value of select http://hg.python.org/cpython/rev/c0a3e17e677f -- nosy: +python-dev ___ Python tracker

[issue12126] incorrect select documentation

Antoine Pitrou added the comment: > It makes sense to bring this up for discussion on pydev, then. Ok, done. > In the meantime, is there an objection to removing the incorrect > statement Jean-Paul mentioned from the doc? Well, no. -- ___ Python t

[issue12126] incorrect select documentation

Eli Bendersky added the comment: It makes sense to bring this up for discussion on pydev, then. Perhaps it will be decided to remove this document from the official documentation, possibly relegating it to the Wiki. In the meantime, is there an objection to removing the incorrect statement J

[issue12126] incorrect select documentation

Antoine Pitrou added the comment: Well, my main issue with this document is that it doesn't seem to have a well-defined destination: - people who know sockets won't learn anything from it - but people who don't know sockets will probably find it clear as mud (for example, what's an "INET" or "

[issue12126] incorrect select documentation

Eli Bendersky added the comment: This issue Jean-Paul raises seems to be a plain error. select() certainly can return that some given socket is both readable and writable (this is explicitly discussed in Steven's APitUE $14.5), and I see no evidence in the implementation of Python's selectmod

[issue12126] incorrect select documentation

Eli Bendersky added the comment: Antoine, can you be more specific? I recall finding it quite useful when first learning Python. Perhaps it can be improved in a few specific places, but overall I don't think it's a bad document. -- nosy: +eli.bendersky ___

[issue12126] incorrect select documentation

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue12126] incorrect select documentation

Antoine Pitrou added the comment: The socket HOWTO looks so stupid, obscure and badly written that it should IMO be deleted. -- nosy: +pitrou ___ Python tracker ___ ___

[issue12126] incorrect select documentation

New submission from Jean-Paul Calderone : http://docs.python.org/py3k/howto/sockets.html#non-blocking-sockets "And if you put a socket in more than one input list, it will only be (at most) in one output list." >>> import socket >>> s = socket.socket() >>> s.connect(('localhost', 22)) >>> imp