Steve Dower <steve.do...@python.org> added the comment:
> Any solution that we apply in Cython will require users to regenerate their > .c sources with a new Cython version in order to make it compile in Py3.8. > The main decision point in this ticket is: should they need to or not? Considering Cython had a bug when it generated those sources (directly using a reserved field), then yes, users should have to regenerate with a fixed version. > My point is that it makes no sense to justify bpo-37221 with the goal of not > breaking Cython modules, when at the same time another change (the one > discussed here) has already broken them. I agree. Here's my distinction: bpo-37221 breaks any user who correctly followed the documentation: https://docs.python.org/3.7/c-api/code.html#c.PyCode_New This issue breaks users who did not follow the documentation: https://docs.python.org/3.7/c-api/typeobj.html#c.PyTypeObject.tp_print ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37250> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
