Message121984
> The Python implementation sets timeout=None (which implies that the
> underlying socket is blocking).
No, it doesn't. A socket may be non-blocking without having a timeout;
that's the socket API (on all systems, not just BSD).
> The problem is that it has. It has created a new Python socket
> object with a specific value for timeout (None), but the underlying
> socket is nonblocking.
>
> The docs state that timeout = None makes the socket blocking.
What specific wording are you looking at that makes you believe so?
To me, the phrase
# A socket object can be in one of three modes: blocking, non-blocking,
# or timeout
suggests otherwise. |
|
Date |
User |
Action |
Args |
2010-11-21 20:41:41 | loewis | set | recipients:
+ loewis, ronaldoussoren, exarkun, roysmith, pitrou, giampaolo.rodola, ned.deily, nicdumz, bbangert, Justin.Cappos |
2010-11-21 20:41:40 | loewis | link | issue7995 messages |
2010-11-21 20:41:40 | loewis | create | |
|