STINNER Victor <vstin...@redhat.com> added the comment:
> Note that PyCode_New() is not the only change in 3.8 beta1 that breaks Cython > generated code. The renaming of "tp_print" to "tp_vectorcall" is equally > disruptive, because Cython has (or had) a work-around for CPython > (mis-)behaviour that reset the field explicitly to NULL after calling > PyType_Ready(), which could set it arbitrarily without good reason. Can someone please open a separated issue to discuss tp_print backward incompatible change? This issue is about PyCode_New(). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37221> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
