On Wed, Jun 17, 2020 at 4:16 AM Steve Dower <steve.do...@python.org> wrote: > > On 16Jun2020 1641, Inada Naoki wrote: > > * This change doesn't affect to pure Python packages. > > * Most of the rest uses Cython. Since I already report an issue to Cython, > > regenerating with new Cython release fixes them. > > The precedent set in our last release with tp_print was that > regenerating Cython releases was too much to ask. > > Unless we're going to overrule that immediately, we should leave > everything there and give users/developers a full release cycle with > updated Cython version to make new releases without causing any breakage. >
We have one year for 3.10 and two years for 3.11. Additionally, unlike the case of tp_print, we don't need to wait all of them are regenerated. Cython used deprecated APIs in two cases: * Cython used PyUnicode_FromUnicode(NULL, 0) to create empty string. Many packages are affected. But we can keep it working when we removed wstr. https://github.com/cython/cython/pull/3677 * Cython used PyUnicode_FromUnicode() in very minor cases. Only few packages are affected. https://github.com/cython/cython/issues/3678 So we need to ask to regenerate with Cython >= 0.9.21 only a few projects. Regards, -- Inada Naoki <songofaca...@gmail.com> _______________________________________________ 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/XGLIVTXIGDEPE5UH32ZGGUCXXQVYXYQN/ Code of Conduct: http://python.org/psf/codeofconduct/
