[issue22475] asyncio task get_stack documentation seems to contradict itself

2014-12-02 Thread Roundup Robot
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

2014-12-02 Thread STINNER Victor
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

[issue22475] asyncio task get_stack documentation seems to contradict itself

2014-09-24 Thread Antoine Pitrou
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +giampaolo.rodola, gvanrossum, haypo, pitrou, yselivanov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22475 ___

[issue22475] asyncio task get_stack documentation seems to contradict itself

2014-09-24 Thread STINNER Victor
Changes by STINNER Victor victor.stin...@gmail.com: -- components: +asyncio ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22475 ___ ___

[issue22475] asyncio task get_stack documentation seems to contradict itself

2014-09-23 Thread R. David Murray
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