Coroutines should be traceable

[mzipay]

Opening this issue as a consolidation of issues/8 and issues/10.

Coroutine tracing support is slated for release 2.0.0 (forthcoming). The plan is to release 1.3.2 and 2.0.0 simultaneously.

Release 1.3.2 will target Python 2.7 and 3.4+ and will not support coroutine tracing, though it will include improved support for tracing generator iterators.

Release 2.0.0 will target only Python 3.4+, will include the improved generator iterator tracing support from 1.3.2, and will introduce coroutine PAUSE/RESUME tracing.

After the simultaneous release of 1.3.2 & 2.0.0, I expect that the 1.x series will only include bugfixes until Python 2.7 EOL in 2020, at which point the entire 1.x series will be "retired."

[mzipay]

Release 1.3.2 is now available. 2.0.0 requires some additional documentation regarding the code base split, so will be delayed a bit (but all tests for coroutine tracing are currently passing, so it is close).

[jp-larose]

Any word on when 2.0 will be released with the fixed tracing for "async def" functions/methods?

I've been using this package to help with some debugging, and it's been great! The issue I'm running into now is I'm only seeing return values of Coroutine for my async funcs, not the actual return value.

[mzipay]

Working on it :)

Most tests are passing, I've just been really busy with "real" work, and the pandemic really impacted my ability to get out to the local coffee shop for evenings of coding. I have a few corner cases still to account for (I don't want to release too early and discover that the coroutine tracing is subpar).

I'm glad autologging has been useful for you!

[Triangulum9r]

can't wait for 2.0. I just started an AsyncIO project and would love to use this library!

[mzipay]

At the moment I am only able to work on the 2.0 changes bit-by-bit on weekends, so it is taking longer than expected. I am hopeful to get the release out in early/mid summer.