On Tue, Nov 30, 2021 at 7:52 PM Victor Stinner <vstin...@python.org> wrote: > For this specific PEP changes, I consider that the number of impacted > projects is low enough to skip a deprecation process: only 4 projects > are known to be impacted. One year ago (Python 3.10), 16 were > impacted, and 12 have already been updated in the meanwhile.
I ran a code search in PyPI top 5000 projects: my tool downloaded 4760 tarball and ZIP archives. On 4760 projects, only 16 of them (0.3%) are affected by the PEP 674: 99.7% (4744) are not affected ;-) IMO it's manageable to help these 16 projects to be updated for Python 3.11 (if the PEP is accepted) before the final version (scheduled for 2022-10-03). I expected that projects would only be affected by Py_TYPE() and Py_SIZE() changes. But I also found exactly 2 projects affected by the PyDescr_TYPE() and PyDescr_NAME() changes: code generated by SWIG in M2Crypto and mecab-python3 projects. I will investigate how to update SWIG for that. More details in the issue: https://bugs.python.org/issue45476#msg407410 Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ 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/YSBCFCJIQWWGDR5WQPDDNUEI4UWKTJ6R/ Code of Conduct: http://python.org/psf/codeofconduct/
