Message345409
| Author |
steve.dower |
| Recipients |
jdemeyer, ncoghlan, petr.viktorin, scoder, steve.dower, vstinner |
| Date |
2019年06月12日.21:18:33 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1560374313.31.0.0925443852651.issue37250@roundup.psfhosted.org> |
| In-reply-to |
| Content |
> 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 |
|