Author neologix
Recipients gvanrossum, haypo, neologix
Date 2014-02-03.08:48:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM09apXJ-TT=hP+s_vk9Z3YRGsBcAYdMaVW6CujsH0sveQ@mail.gmail.com>
In-reply-to <1391390675.63.0.526015486625.issue20493@psf.upfronthosting.co.za>
Content
> Shouldn't this be fixed in the C implementation of the select module or
in selectors.py? It seems likely that the exact range might be different
for each syscall and possibly per OS or even OS version.

Agreed: if we want to fix this, it should be done in the select module.

I'm saying "if", because we could either consider such a large timeout as
an error and report it (like it's currently done), or silently cap the
timeout.
The later approach is used by libevent, and makes sense, to a certain
extent (we just need to consider whether this can cause backward
compatibility issues).
History
Date User Action Args
2014-02-03 08:48:23neologixsetrecipients: + neologix, gvanrossum, haypo
2014-02-03 08:48:23neologixlinkissue20493 messages
2014-02-03 08:48:23neologixcreate