Message 308957 - Python tracker

➜

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	yselivanov
Recipients	asvetlov, yselivanov
Date	2017-12-23.16:59:10
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
Currently, asyncio code accesses Future._loop and Task._loop property to validate the event loop and implement functions like "Task.all_tasks()". So the "_loop" is a semi-official public API that other Task & Future implementations must follow in order to be compatible with asyncio code. I propose to add Future.get_loop() and Task.get_loop() methods, and soft-deprecate ._loop property.

Currently, asyncio code accesses Future._loop and Task._loop property to validate the event loop and implement functions like "Task.all_tasks()".  So the "_loop" is a semi-official public API that other Task & Future implementations must follow in order to be compatible with asyncio code.

I propose to add Future.get_loop() and Task.get_loop() methods, and soft-deprecate ._loop property.

History
Date	User	Action	Args
2017-12-23 16:59:11	yselivanov	set	recipients: + yselivanov, asvetlov
2017-12-23 16:59:11	yselivanov	set	messageid: <[email protected]>
2017-12-23 16:59:11	yselivanov	link	issue32415 messages
2017-12-23 16:59:10	yselivanov	create