Le mar. 23 juin 2020 à 04:02, Inada Naoki email@example.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.