Sorry, ignore my comment: Cython no longer uses PyUnicode_FromString(NULL, 0) in the master branch. The change was backported to the 0.29.x branch, but this stable branch requires a second fix, so I wrote it: https://github.com/cython/cython/pull/3721
Victor Le ven. 3 juil. 2020 à 16:00, Victor Stinner <vstin...@python.org> a écrit : > > Le sam. 13 juin 2020 à 12:39, Inada Naoki <songofaca...@gmail.com> a écrit : > > Of course, there is an API to create an empty string: PyUnicode_New(0, 0); > > But since Cython is using `PyUnicode_FromString(NULL, 0)`, > > keep it working for some versions will mitigate the breaking change. > > Note that we can remove wchar_t cache while keeping it working. > > > > Anyway, this is an idea for mitigation. If all of maintained packages > > fixes it > > before Python 3.11, mitigation is not needed. > > Can someone propose a Cython PR to use PyUnicode_New(0, 0) on Python > 3.3 and newer, or PyUnicode_FromString(NULL, 0) on old Python > versions? > > Victor > -- > Night gathers, and now my watch begins. It shall not end until my death. -- 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/WJNIG4VY32DJUYPTK3GPIE2VKG4DDZEQ/ Code of Conduct: http://python.org/psf/codeofconduct/
