[issue22475] asyncio task get_stack documentation seems to contradict itself

STINNER Victor added the comment: I fixed the most obvious issue in the documentation. I don't know the function enough to propose a better documentation, sorry. Don't hesitate to write a patch on the documentation if you have a better explanation of how get_stack() behaves. It is correct tha

[issue22475] asyncio task get_stack documentation seems to contradict itself

Roundup Robot added the comment: New changeset 4b6b03c1f4ff by Victor Stinner in branch '3.4': Closes #22475: asyncio doc, fix Task.get_stack() doc https://hg.python.org/cpython/rev/4b6b03c1f4ff -- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed __

[issue22475] asyncio task get_stack documentation seems to contradict itself

Changes by STINNER Victor : -- components: +asyncio ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue22475] asyncio task get_stack documentation seems to contradict itself

Changes by Antoine Pitrou : -- nosy: +giampaolo.rodola, gvanrossum, haypo, pitrou, yselivanov ___ Python tracker ___ ___ Python-bugs-l

[issue22475] asyncio task get_stack documentation seems to contradict itself

New submission from R. David Murray: The get_stack method docs say: "If the coroutine is active, returns the stack where it was suspended." I presume this means something more like "if the coroutine is not done...", since in English you can't be both active *and* suspended. Or does it mean "