[docs] [issue22474] No explanation of how a task gets destroyed in asyncio 'task' documentation
R. David Murray
report at bugs.python.org
Wed Sep 24 02:02:23 CEST 2014
New submission from R. David Murray:
In https://docs.python.org/3/library/asyncio-task.html#task, there is a note about a warning being logged if a pending task is destroyed. The section does not explain or link to an explanation of how a task might get destroyed. Nor does it define pending, but that seems reasonably clear from context (ie: the future has not completed).
The example linked to does not show how the pending task got destroyed, it only shows an example of the resulting logging, with not enough information to really understand what the final line of the error message is reporting (is kill_me an asyncio API, or the name of the task, or the future it is wrapping?)
----------
assignee: docs at python
components: Documentation
messages: 227400
nosy: docs at python, r.david.murray
priority: normal
severity: normal
status: open
title: No explanation of how a task gets destroyed in asyncio 'task' documentation
type: behavior
versions: Python 3.4, Python 3.5
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22474>
_______________________________________
More information about the docs
mailing list