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 aeros
Recipients aeros, asvetlov, uriyyo, yselivanov
Date 2020-11-24.23:15:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1606259732.88.0.515777612818.issue42392@roundup.psfhosted.org>
In-reply-to
Content
> Is there anyone who is assigned to removing the deprecated `loop` parameter from `asyncio` codebase?

> If not I can take this task, I believe I have enough free time and curiosity to do that :)

You can certainly feel free to work on that and it would definitely be appreciated! However, I would recommend splitting it into several PRs, basically as "Remove *loop* parameter from x` rather than doing a massive PR that removes it from everywhere that it was deprecated. This makes the review process easier.

Also, keep in mind that there are some uses of *loop* that are still perfectly valid and will remain so, such as in `asyncio.run_coroutine_threadsafe()`. It should only be removed in locations where there was a deprecation warning from 3.8 or sooner present (as we give two major versions of deprecation notice before most breaking changes are made -- this has been made official policy as of PEP 387).
History
Date User Action Args
2020-11-24 23:15:32aerossetrecipients: + aeros, asvetlov, yselivanov, uriyyo
2020-11-24 23:15:32aerossetmessageid: <1606259732.88.0.515777612818.issue42392@roundup.psfhosted.org>
2020-11-24 23:15:32aeroslinkissue42392 messages
2020-11-24 23:15:32aeroscreate