AFAIK No any guarantee On Tue, Jun 27, 2017 at 10:29 AM Chris Jerdonek <chris.jerdo...@gmail.com> wrote:
> I have a couple questions about asyncio's synchronization primitives. > > Say a coroutine acquires an asyncio Condition's underlying lock, calls > notify() (or notify_all()), and then releases the lock. In terms of > which coroutines will acquire the lock next, is any preference given > between (1) coroutines waiting to acquire the underlying lock, and (2) > coroutines waiting on the Condition object itself? The documentation > doesn't seem to say anything about this. > > Also, more generally (and I'm sure this question gets asked a lot), > does asyncio provide any guarantees about the order in which awaiting > coroutines are awakened? For example, for synchronization primitives, > does each primitive maintain a FIFO queue of who will be awakened > next, or are there no guarantees about the order? > > Thanks a lot, > --Chris > _______________________________________________ > Async-sig mailing list > Async-sig@python.org > https://mail.python.org/mailman/listinfo/async-sig > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- Thanks, Andrew Svetlov
_______________________________________________ Async-sig mailing list Async-sig@python.org https://mail.python.org/mailman/listinfo/async-sig Code of Conduct: https://www.python.org/psf/codeofconduct/
