Message345318
> 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(). |
|
| Date |
User |
Action |
Args |
| 2019-06-12 11:33:53 | vstinner | set | recipients:
+ vstinner, nascheme, ncoghlan, scoder, petr.viktorin, lukasz.langa, serhiy.storchaka, jdemeyer, pablogsal |
| 2019-06-12 11:33:53 | vstinner | set | messageid: <[email protected]> |
| 2019-06-12 11:33:53 | vstinner | link | issue37221 messages |
| 2019-06-12 11:33:53 | vstinner | create | |
|