Message 381275 - 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	2020-11-17.19:04:05
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1605639845.5.0.800535008799.issue42392@roundup.psfhosted.org>
In-reply-to

Content
asyncio.Lock and other primitives should no longer accept the `loop` parameter. They should also stop storing the current loop in the `self._loop` attribute. Instead, they should use `get_running_loop()` whenever they need to access the loop.

asyncio.Lock and other primitives should no longer accept the `loop` parameter. They should also stop storing the current loop in the `self._loop` attribute. Instead, they should use `get_running_loop()` whenever they need to access the loop.

History
Date	User	Action	Args
2020-11-17 19:04:05	yselivanov	set	recipients: + yselivanov, asvetlov
2020-11-17 19:04:05	yselivanov	set	messageid: <1605639845.5.0.800535008799.issue42392@roundup.psfhosted.org>
2020-11-17 19:04:05	yselivanov	link	issue42392 messages
2020-11-17 19:04:05	yselivanov	create