Ewald de Wit

``` coro0: 0 coro1: 0 coro2: 0 coro3: 0 coro4: 0 coro5: 0 coro6: 0 coro7: 0 coro8: 0 coro9: 0 PING 0.10097742080688477 coro9: 1 PING 0.20212650299072266 coro9: 2 PING...

The only possible WTF moment is the first step of each task, which are executed all at the beginning. This is due to an optimization for ``asyncio.sleep(0)`` by asyncio. The...

This fix had to be reverted.

There is not much to go on from these reports, but I suspect it has to do with multithreading. The new v1.5.5 release might offer an improvement in this regard

> RuntimeError: Cannot enter into task This error is indicative of an unpatched Task. It could be similar to the unpatched Future from #23, were it gets imported before nest_asyncio...

There is the original discussion thread [here](https://bugs.python.org/issue22239), where the explicit decision is made to not allow nesting. The main objection by GvR is > very hard to debug problems that...

That's a great idea @davidbrochart. I think if the asyncio authors do want nesting then it might be easier for them to modify their own code then it is to...

The process_events coroutine at the start of this thread has the slight drawback that it doesn't handle DefferedDelete events, as mentioned in the [Qt docs](http://doc.qt.io/qt-5/qcoreapplication.html#processEvents). I noticed this when using...

It turns out that the loop in my previous post has the drawback of not firing QApplication events, such as aboutToQuit and lastWindowClosed. What works very well for me as...

What seems to work well in practice is to use something between L1 and L2 normalization. This is what I use for HiFiScan: https://github.com/erdewit/HiFiScan/blob/7b41e81d3e56f9c92a10508418926e22a5ccea97/hifiscan/analyzer.py#L273