> 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/
