Message345969
| Author |
jdemeyer |
| Recipients |
jdemeyer, ncoghlan, petr.viktorin, scoder, steve.dower, vstinner |
| Date |
2019年06月18日.09:07:26 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1560848846.93.0.624633964187.issue37250@roundup.psfhosted.org> |
| In-reply-to |
| Content |
> If we reintroduce it, why not put it back at its previous place, to provide ABI compatibility?
First of all, we longer care about ABI compatibility of PyTypeObject.
Second, it is extremely unlikely that the class will use vectorcall: the only way would be to inherit from a base class that uses vectorcall, but there aren't any subclassable classes using vectorcall in CPython. If the class doesn't use vectorcall, then it really doesn't matter: tp_vectorcall_offset is unused in that case, just like tp_print. |
|