Message345318
| Author |
vstinner |
| Recipients |
jdemeyer, lukasz.langa, nascheme, ncoghlan, pablogsal, petr.viktorin, scoder, serhiy.storchaka, vstinner |
| Date |
2019年06月12日.11:33:53 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1560339233.63.0.593106326118.issue37221@roundup.psfhosted.org> |
| In-reply-to |
| Content |
> 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(). |
|