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 kristjan.jonsson
Recipients alex.gronholm, brian.curtin, kristjan.jonsson, mark.dickinson, pitrou, r.david.murray, raruler, tim.golden
Date 2014-05-07.21:40:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ah, I saw this code here in thread_nt.h:

if ((DWORD) milliseconds != milliseconds)
            Py_FatalError("Timeout too large for a DWORD, "
                           "please check PY_TIMEOUT_MAX");

the PyCOND_TIMEDWAIT is currently only used by the GIL code and by the locks on NT.  The GIL code assumes microsecond resolution.  So we need to stick to that, at least.  But the locking code assumes at least DWORD worth of milliseconds.
Date User Action Args
2014-05-07 21:40:21kristjan.jonssonsetrecipients: + kristjan.jonsson, mark.dickinson, pitrou, tim.golden, r.david.murray, brian.curtin, alex.gronholm, raruler
2014-05-07 21:40:21kristjan.jonssonsetmessageid: <>
2014-05-07 21:40:21kristjan.jonssonlinkissue20737 messages
2014-05-07 21:40:20kristjan.jonssoncreate