[issue22875] asyncio: call_soon() documentation unclear on timing

STINNER Victor added the comment: FYI I added a new test to the aiotest project (test suite for asyncio), for this issue: https://bitbucket.org/haypo/aiotest/commits/17dd11fc2f4bafad623f940b1a33a3b8b0d39ccd -- ___ Python tracker

[issue22875] asyncio: call_soon() documentation unclear on timing

STINNER Victor added the comment: Oops, I forgot to mention the issue number in my commit. changeset: 93893:a59fed8c710b branch: 3.4 parent: 93891:1da9e9eaeae8 user:Victor Stinner date:Mon Dec 15 17:50:55 2014 +0100 files: Doc/library/asyncio-eventloop.rst desc

[issue22875] asyncio: call_soon() documentation unclear on timing

STINNER Victor added the comment: Thanks Martin for your change, I commited it. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue22875] asyncio: call_soon() documentation unclear on timing

Guido van Rossum added the comment: Docfix LGTM. On Fri, Dec 12, 2014 at 10:53 PM, Martin Panter wrote: > > > Martin Panter added the comment: > > I have been bitten by this when attempting to implement my own event > loops. Parts of the “asyncio” code itself expects that the callback is not >

[issue22875] asyncio: call_soon() documentation unclear on timing

Martin Panter added the comment: I have been bitten by this when attempting to implement my own event loops. Parts of the “asyncio” code itself expects that the callback is not invoked directly after call_soon() returns. Here is a simple patch. -- keywords: +patch nosy: +vadmium versio

[issue22875] asyncio: call_soon() documentation unclear on timing

R. David Murray added the comment: Personally, when I read that I thought "arrange for" made it pretty clear it was when control returned to the event loop, but I agree that if it can be made clearer it should be. -- nosy: +r.david.murray ___ Python

[issue22875] asyncio: call_soon() documentation unclear on timing

Guido van Rossum added the comment: "As soon as possible" is constrained by "all callbacks are called from the event loop". Feel free to suggest a doc patch (asyncio docs are in dire need of more help!) -- ___ Python tracker

[issue22875] asyncio: call_soon() documentation unclear on timing

New submission from Corbin Simpson: Hi there! While assisting somebody on #python (where manners go to die), I was consulting asyncio's documentation. Given my unfamiliarity with asyncio, I was surprised to read BaseEventLoop.call_soon()'s documented behavior: "Arrange for a callback to be ca