Message113754
The wait loop in Condition.wait() has disappeared under 3.2 (we use builtin lock-with-timeout primitives instead).
Overall, I don't think this issue is very important. Changing the system time *backwards* can cause all kinds of issues in daemons and other long-running programs, which generally assume a monotonous time function. Also, it could be disputed what the preferred semantics are (observe "real" time or observe the computer clock), and the answer is probably application-specific. |
|
Date |
User |
Action |
Args |
2010-08-13 10:30:45 | pitrou | set | recipients:
+ pitrou, jimjjewett, qopit, jtate, xiaowen |
2010-08-13 10:30:45 | pitrou | set | messageid: <1281695445.24.0.673733783715.issue1508864@psf.upfronthosting.co.za> |
2010-08-13 10:30:44 | pitrou | link | issue1508864 messages |
2010-08-13 10:30:43 | pitrou | create | |
|