[Python-bugs-list] [ python-Bugs-657469 ] Determining timed-out on Condition wait
noreply@sourceforge.net
noreply@sourceforge.net
Sun, 22 Dec 2002 13:15:30 -0800
Bugs item #657469, was opened at 2002-12-22 13:19
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=657469&group_id=5470
Category: None
>Group: Not a Bug
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Martin v. Löwis (loewis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Determining timed-out on Condition wait
Initial Comment:
threading.Condition.wait currently does not report
whether the condition was triggered, or whether a
timeout occurred.
----------------------------------------------------------------------
>Comment By: Martin v. Löwis (loewis)
Date: 2002-12-22 22:15
Message:
Logged In: YES
user_id=21627
Somebody suggested that this would be desirable; I now see
it is not. Closing as not-a-bug.
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2002-12-22 18:21
Message:
Logged In: YES
user_id=31435
Martin, why do you consider this to be a bug? Proper use
of the condition *protocol* requires checking whether the
state you're wating for actually obtains after a wait()
returns, and looping back to try again if the state doesn't
obtain. The invariant promised by the condition protocol is
simply that the condition is acquired whenever wait()
returns (for whatever reason, be it signal, timeout,
KeyboardInterrupt, SystemExit, ...).
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=657469&group_id=5470