To be honest, based on my basic skills on AsyncIO, it isn't the behaviour I've in my mind.
The explicit stop() before run_forever() should give a complete result list. I see run_forever() as a start() I can understand why it's half-processed, but, at least for me, it's a little bit counter-intuitive. Now, this point is an yocto detail, if everybody is ok with that, no problems. -- Ludovic Gasc On Thu, Feb 12, 2015 at 1:17 PM, Victor Stinner <[email protected]> wrote: > Hi, > > I wrote the aiotest test suite to check if an implementation of the > PEP 3156 is compliant with PEP. I wrote a test to ensure that > functions scheduled with call_soon() after a call to stop() are not > executed before the next call to run_forever(): > > > https://bitbucket.org/haypo/aiotest/src/22ecbabe626874bb30a801a49bc87568fadf3fcc/aiotest/test_callback.py?at=default#cl-34 > > Is my test too strict, or do implementations respect this restriction? > > Victor >
