tree e44d7ac1b3483da0f95a9f95e6907c1d5036a242
parent e1179a5096fb12297ececd7a1c79969aa5747e28
author Petr Viktorin <encukou@gmail.com> 1559512340 +0200
committer GitHub <noreply@github.com> 1559512340 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJc9EUUCRBK7hj4Ov3rIwAAdHIIAAHRXtrGlPIlOi1d3LqjBhis
 pMDtb99OGYDnQ3pwdqTEvy2husZTkvJH1ioeXKSGcTnkGQSDTUhoBRMeAmZ993ES
 YzZHU8TypHRXSVIOzOr4gwyQTaLm3MwDg6NaDZ4M3ln9N04NfA98MQVHc0qyJ3aP
 +e606xE5TMbrvReQTfZcjavSPIqUo2xiOxz5NVR+eMhDvrdH3TqPhU+2rX6RY1jt
 sOL4Xu0aV/ZlJtcMuy7nY0BrIPAvP2Kjge0R4/5JOKJ2ongkMRQmFzIYX4aFkMqr
 fMVYFQdPKNZbURHycwY3ANxYWOWEA5Fo8mbz1gnKpygAxkWPNQ4XoRs8IoKFASk=
 =uPWn
 -----END PGP SIGNATURE-----
 

bpo-36974: Make tp_call=PyVectorcall_Call work for inherited types (GH-13699)

When inheriting a heap subclass from a vectorcall class that sets
`.tp_call=PyVectorcall_Call` (as recommended in PEP 590), the subclass does
not inherit `_Py_TPFLAGS_HAVE_VECTORCALL`, and thus `PyVectorcall_Call` does
not work for it.

This attempts to solve the issue by:
* always inheriting `tp_vectorcall_offset` unless `tp_call` is overridden
  in the subclass
* inheriting _Py_TPFLAGS_HAVE_VECTORCALL for static types, unless `tp_call`
  is overridden
* making `PyVectorcall_Call` ignore `_Py_TPFLAGS_HAVE_VECTORCALL`

This means it'll be ever more important to only call `PyVectorcall_Call`
on classes that support vectorcall. In `PyVectorcall_Call`'s intended role
as `tp_call` filler, that's not a problem.