-1 I'm OK with current asyncio locks and queue implementation, they are not-threadsafe by design explicitly.
For locks you can use `yield from lock.acquire()` (requires nested function definition for passing into `loop.call_soon_threadsafe()`) and `lock.release()`. I personally don't like to add strictness for asyncio implementations: that may lead to performance degradations and may make problems for writing non-standard event loops. On Wed, Feb 25, 2015 at 4:57 PM, Ludovic Gasc <gml...@gmail.com> wrote: > On Wednesday, February 25, 2015 at 2:43:54 PM UTC+1, Victor Stinner wrote: >> >> Maybe we should modify asyncio.Queue and asyncio.Lock to make them >> thread-safe? > > > For me, it's the ideal scenario, but: > 1. I have no idea if it's complicated > 2. If it should reduce performances when you don't use threads -- Thanks, Andrew Svetlov
