Re: [Async-sig] Asyncio loop instrumentation
>>> For this proposal [4], POC, I've preferred make a reduced list of events: >>> >>> * `loop_start` : Executed when the loop starts for the first time. >>> * `tick_start` : Executed when a new loop tick is started. >>> * `io_start` : Executed when a new IO process starts. >>> * `io_end` : Executed when the IO process ends. >>> * `tick_end` : Executed when the loop tick ends. >>> * `loop_stop` : Executed when the loop stops. >> >> What do you call a "IO process" in this context? > > Basically the call to the `select/poll/whatever` syscall that will ask > for read or write to a set of file descriptors. `select/poll/whatever` syscalls doesn't ask for read or write. It waits for read or write (more accurate, waits for readable or writable state). So poll_start / poll_end looks better name to me. INADA Naoki > > Thanks, > > -- > --pau > ___ > 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/ ___ 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/
Re: [Async-sig] [python-tulip] Python 3.6b2 will have C implemented Future
Thank you for information. I'll look it, hopefully in next week. 2016/10/15 午前2:24 "Julien Duponchelle" : > On Sun, Oct 9, 2016 at 8:06 AM Naoki INADA wrote: > >> Hi. >> >> I've just pushed C implementation of asyncio.Future [1]. >> It will be included in Python 3.6b2. >> >> It may have rough edge. But I hope it will be battle tested >> before Python 3.6.0. >> Please help us by running your tests on Python 3.6b2, and >> report issues you found. >> If you have asyncio based project, and it uses Travis-CI, >> please add "nightly" to your .travis.cnf [2]. >> >> Feedback about performance difference is also welcome. >> >> Thanks, >> >> [1]: https://hg.python.org/cpython/rev/678424183b38 >> [2] https://docs.travis-ci.com/user/languages/python/# >> Choosing-Python-versions-to-test-against >> > > Hi, > > I have setup a 3.6 build on Travis of our project GNS3 and it seem to fail. > https://travis-ci.org/GNS3/gns3-server/builds/167703118 > > To be honest I didn't dig the issue and could be wrong usage of asyncio > (or ugly mock in tests). But this could perhaps interest you. > > I think the most interresting test is: > https://travis-ci.org/GNS3/gns3-server/jobs/167702085#L2270 > > Because we test a websocket client server connection. > > Thanks a lot for your work > ___ 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/
Re: [Async-sig] [python-tulip] Python 3.6b2 will have C implemented Future
Thanks, Ben. Both are very helpful information! On Thu, Oct 13, 2016 at 2:25 PM, Ben Darnell wrote: > [+async-sig@python.org, which is the new home for these kinds of > discussions] > > Tornado's tests are now failing on nightly with "TypeError: can't send > non-None value to a FutureIter": > https://travis-ci.org/tornadoweb/tornado/jobs/167252979 > > -Ben > > On Tue, Oct 11, 2016 at 3:55 PM INADA Naoki wrote: >> >> > If you have asyncio based project, and it uses Travis-CI, >> >> > please add "nightly" to your .travis.cnf [2]. >> >> > >> >> > [2] >> >> > >> > https://docs.travis-ci.com/user/languages/python/#Choosing-Python-versions-to-test-against >> >> >> >> Travis changed the "nightly" version to 3.7 >> >> Now "3.6-dev" is for Python 3.6beta (Still 3.6b1, it may be upgraded >> soon). >> >> >> >> -- >> >> INADA Naoki >> > -- INADA Naoki ___ 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/
