[issue46892] Async Call-Stack Reconstruction

Andrew Svetlov added the comment: The idea looks interesting. The devil in the details I guess. I'm curious what is the memory and performance penalty. Waiting for the PR as the discussion starting point. -- ___ Python tracker

[issue46892] Async Call-Stack Reconstruction

Guido van Rossum added the comment: I've recently dabbled a bit in some new primitives for asyncio, and based on that experience I think this would be very useful. IIRC Trio does this (presumably at considerable cost) in userland. -- ___ Python

[issue46892] Async Call-Stack Reconstruction

Matt Page added the comment: Sorry for the confusion, I'm working on a PR. I filed the BPO to gauge interest in the feature. -- ___ Python tracker ___

[issue46892] Async Call-Stack Reconstruction

Change by Kumar Aditya : -- nosy: +gvanrossum, kumaraditya303 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46892] Async Call-Stack Reconstruction

Andrew Svetlov added the comment: > We’d like to merge our implementation into CPython Could you provide a link first, please? -- ___ Python tracker ___

[issue46892] Async Call-Stack Reconstruction

New submission from Matt Page : Profiling tools that use the call-stack (i.e. all of them) paint an incomplete picture of what’s really going on in async-heavy codebases. They can only show the stack of the currently executing task; they miss the chain of awaitables that are transitively