[New-bugs-announce] [issue22475] asyncio task get_stack documentation seems to contradict itself

R. David Murray report at bugs.python.org
Wed Sep 24 02:51:49 CEST 2014

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 "last suspended"?

Then it talks about limit and how stacks limit returns newest frames while with tracebacks it is oldest frames...but the last sentence says that for suspended coroutines only one frame is returned.

So there is a definite lack of clarity here: can we get multiple frames if the coroutine is not suspended (in which case that first sentence seems likely to be the 'last suspended' interpretation), or for non-tracebacks can we only ever get one frame, in which case why talk about limit returning the newest frames for stacks?

assignee: docs at python
components: Documentation
messages: 227401
nosy: docs at python, r.david.murray
priority: normal
severity: normal
status: open
title: asyncio task get_stack documentation seems to contradict itself
type: behavior
versions: Python 3.4, Python 3.5

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list