select(sock) indicates not-ready, but sock.recv does not block

Nikolaus Rath Nikolaus at
Mon Feb 17 07:35:22 CET 2014


I have a problem with using select. I can reliably reproduce a situation
where,), (), (), 0) returns ((),(),())
(i.e., no data ready for reading), but an immediately following
sock.recv() returns data without blocking.

I am pretty sure that this is not a race condition. The behavor is 100%
reproducible, the program is single threaded, and even waiting for 10
seconds before the select() call does not change the result.

I'm running Python 3.3.3 under Linux 3.12.

Has anyone an idea what might be going wrong here?


Encrypted emails preferred.
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C

             »Time flies like an arrow, fruit flies like a Banana.«

More information about the Python-list mailing list