[issue29303] asyncio.Lock.acquire() does not always yield

2017-01-17 Thread anonymous2017
anonymous2017 added the comment: I may have mis-characterized the original report. Rephrasing just to make sure it is correctly addressed: First, it is not about fairness. Sorry for the original characterization. I was trying to understand what was happening. Second, the precise issue

[issue29303] asyncio.Lock.acquire() does not always yield

2017-01-17 Thread anonymous2017
New submission from anonymous2017: Details here: http://stackoverflow.com/questions/41708609/unfair-scheduling-bad-lock-optimization-in-asyncio-event-loop Essentially there should be a `yield` before this line otherwise a coroutine that only acquires and releases a lock will never yield