This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author asvetlov
Recipients asvetlov, docs@python, kj, miss-islington, serhiy.storchaka, yselivanov
Date 2022-02-18.10:40:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645180845.4.0.104251111417.issue46777@roundup.psfhosted.org>
In-reply-to
Content
> 6. The loop parameter of Task() was documented as both removed and required (if there is no current event loop) in 3.10.

I think we should drop Task() constructor definition from Task Object docs https://docs.python.org/3/library/asyncio-task.html#task-object but create 'asyncio-extending.rst' (suggest better name please) with low-level task documentation for guys who want to create their own task class.

Task constructor could be documented here along with `_register_task()`, `_enter_task()`, `_leave_task()`, `_unregister_task()`. They might be useful for ones who implements a custom task factories.
History
Date User Action Args
2022-02-18 10:40:45asvetlovsetrecipients: + asvetlov, docs@python, serhiy.storchaka, yselivanov, miss-islington, kj
2022-02-18 10:40:45asvetlovsetmessageid: <1645180845.4.0.104251111417.issue46777@roundup.psfhosted.org>
2022-02-18 10:40:45asvetlovlinkissue46777 messages
2022-02-18 10:40:45asvetlovcreate