Le mar. 23 juin 2020 à 04:02, Inada Naoki <songofaca...@gmail.com> a écrit : > Legacy unicode representation is using wstr so legacy unicode support > is removed with wstr. > PyUnicode_READY() will be no-op when wstr is removed. We can remove > calling of PyUnicode_READY() since then. > > I think we can deprecate PyUnicode_READY() when wstr is removed.
Would it be possible to rewrite the plan differently (merge Specification sections) to list changes per Python version? Something like: == Python 3.9 == * Deprecate xxx in the documentation and add Py_DEPRECATED() * Remove xxx == Python 3.10 == * Deprecate xxx in the documentation and add Py_DEPRECATED() * Add DeprecationWarning at runtime in xxx * Remove xxx == Python 3.11 == * Remove wstr member * Remove xxx functions * PyUnicode_READY() is kept for backward compatibility but it deprecated and becomes as no-opt * ... == Python 3.12 == * Remove PyUnicode_READY() * ... Also, some functions are already deprecated. Would you mind to list them in the PEP? I fail to track the status of each function. Victor _______________________________________________ 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/3VMF2CB2K5NTFUUUNOFJ6R52I2OMTF55/ Code of Conduct: http://python.org/psf/codeofconduct/
