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 bkabrda
Recipients bkabrda
Date 2013-04-16.09:22:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366104172.5.0.472723952105.issue17748@psf.upfronthosting.co.za>
In-reply-to
Content
On Python 2, Condition.wait timeout is always taken as

min(delay * 2, remaining, .05)

which means it cannot be longer than 50 ms. I don't see a reason for this and AFAIK this is no longer true for Python 3, where timeout can be arbitrarily long. Would it be possible to replace the min() call with just "remaining" completely? If not, would it at least be possible to add an argument to wait(), that would trigger this behaviour (something like patch suggested by Jaroslav Skarvada [1] who reported this issue at [2])?

Thanks.

[1] https://bugzilla.redhat.com/attachment.cgi?id=736029&action=diff
[2] https://bugzilla.redhat.com/show_bug.cgi?id=917709
History
Date User Action Args
2013-04-16 09:22:52bkabrdasetrecipients: + bkabrda
2013-04-16 09:22:52bkabrdasetmessageid: <1366104172.5.0.472723952105.issue17748@psf.upfronthosting.co.za>
2013-04-16 09:22:52bkabrdalinkissue17748 messages
2013-04-16 09:22:51bkabrdacreate