Victor Stinner

IMO we should put more tests in aiotest first. For call_soon, stop, call_soon: the test validates asynioc spec. Maybe I misunderstood the spec and it should be discussed on the...

> I haven't looked into it, but IIRC call_soon is specified quite loosely, so I guess it's possible 2 implementations differ a little there, while both being compliant. I write...

About runtests.py: having to clone the asyncio repository is not convinient. You can drop runtests.py right now, but reminder to replace it with something else later ;-) The most important...

> @haypo Do you see some use cases to add tests for aiouv but not for aiotest ? You can take a look at asyncio, it has +800 tests. But...

2015-02-12 17:59 GMT+01:00 Ludovic Gasc [email protected]: > aiouv private API testing => we need to have a test suite. Anybody has an objection to use py.test ? I already use...

Another example. In https://bugs.python.org/issue47075 I explicitly wrote ``I proposed GH-32112 for that.`` to get a link to my PR https://github.com/python/cpython/pull/32112 but the converted issue https://github.com/python/cpython/issues/91231 points to https://github.com/python/cpython/issues/76293 i don't...

> The transfer tool thought that your GH-32112 was a reference to [bpo-32112](https://bugs.python.org/issue?@action=redirect&bpo=32112) Would it be possible to process all data once more time to detect the issue and fix...

> when we discussed different options to edit the messages after the fact and they all changed the "last updated" field (technically GitHub could rewrite the messages directly in the...

You should write the result into a JSON file, and then analyze the data: https://pyperf.readthedocs.io/en/latest/analyze.html pyperf is now well tuned for JIT compilers. You may have to adjust parameters like...

cc @cfbolz @corona10 See also issues like #128