This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients jdemeyer, petr.viktorin, scoder, vstinner
Date 2019-06-12.13:47:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560347255.02.0.420166742386.issue37250@roundup.psfhosted.org>
In-reply-to
Content
> Or maybe you're confusing tp_vectorcall_offset and tp_vectorcall again?

The two are related, no?

Honestly, reintroducing tp_print looks simple and safe enough. I'm in favor of doing that. Is there any drawback? (as I wrote, I don't think that the size of PyTypeObject really matters in practice)
History
Date User Action Args
2019-06-12 13:47:35vstinnersetrecipients: + vstinner, scoder, petr.viktorin, jdemeyer
2019-06-12 13:47:35vstinnersetmessageid: <1560347255.02.0.420166742386.issue37250@roundup.psfhosted.org>
2019-06-12 13:47:35vstinnerlinkissue37250 messages
2019-06-12 13:47:34vstinnercreate