[Python-Dev] Existing asyncio features scheduled for removal in Python 3.9 and 3.10
Hi everyone, There are a couple of uncompleted asyncio feature removals scheduled for 3.9 and 3.10 releases. It will be great if we either complete them or reschedule before the 3.10 feature freeze. There are two stale pull requests related to this. Removal of @asyncio.coroutine in version 3.10 deprecated since version 3.8 Documentation: https://docs.python.org/3.10/library/asyncio-task.html#asyncio.coroutine Issue deprecating the decorator: https://bugs.python.org/issue36921 Issue for the removal: https://bugs.python.org/issue43216 There is no pull request yet, mainly because of an unclarified question regarding types.coroutine in 36921. Prohibiting non-ThreadPoolExecutor in loop.set_default_executor Warning scheduling the prohibiting in version 3.9: https://github.com/python/cpython/blob/425434dadc30d96dc1c0c628f954f9b6f5edd2c9/Lib/asyncio/base_events.py#L816-L821 Issue: https://bugs.python.org/issue43234 Stale pull request: https://github.com/python/cpython/pull/24540 Prohibiting previously deprecated operations on asyncio.trsock.TransportSocket Warning scheduling the prohibiting in version 3.9: https://github.com/python/cpython/blob/425434dadc30d96dc1c0c628f954f9b6f5edd2c9/Lib/asyncio/trsock.py#L20-L24 Issue: https://bugs.python.org/issue43232 Stale pull request: https://github.com/python/cpython/pull/24538 Thanks, Illia ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/PLSLFTJXY2JUIRGJARBER4SRUWDXX2AQ/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Existing asyncio features scheduled for removal in Python 3.9 and 3.10
> I would prefer to wait for 3.11 to remove more deprecated features, > these ones can survive a little bit longer. > > If possible, I suggest to remove functions at the beginning of a new > Python development cycle, rather than just before the feature freeze. > So projects tested with the development branch of Python can detect > issues early and we can more time to either fix these projects, or to > consider reverting the removals to give more time for updating these > projects. Fair enough, Victor :) > It's common that we forget to remove deprecated functions and so that > documentation is not accurate. IMO it's not a big deal ;-) Do you think it is worth updating the documentation and warnings related to the asyncio features to state that they will be removed in Python 3.11 instead of 3.9 or 3.10? ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/SKHD2UNBGCVHTDDJ3O3YB7PXEB6CTDPU/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Does ensurepip still have to include a copy of setuptools?
Hi everyone, ensurepip includes private copies of pip and setuptools. But PEP 453 states that "once pip is able to run pip install --upgrade pip without needing setuptools installed first, then the private copy of setuptools will be removed from ensurepip in subsequent CPython releases." https://www.python.org/dev/peps/pep-0453/#automatic-installation-of-setuptools At the moment pip itself includes a needed part of setuptools. https://github.com/pypa/pip/tree/9c474d4862907ae220ced0fcdbd76660955ff732/src/pip/_vendor/pkg_resources I experimented with modifying ensurepip in the main branch not to install setuptools, and then used it to install pip. It worked fine. Then I run `./python -m pip install --upgrade pip`, and it upgraded pip successfully. Does this mean that we can drop the copy of setuptools? Note, the venv module has such code `CORE_VENV_DEPS = ('pip', 'setuptools')`. I am not sure whether it requires setuptools from ensurepip. Thanks, Illia ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/3BVAUIQOEOXAULHVYQNLLQIZQQETX2EV/ Code of Conduct: http://python.org/psf/codeofconduct/