➜

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.

作者 jdemeyer
收信人 jdemeyer, lukasz.langa, nascheme, ncoghlan, pablogsal, petr.viktorin, scoder, serhiy.storchaka, vstinner
日期 2019-06-12.09:38:07
SpamBayes Score -1.0
Marked as misclassified 是
Message-id <1560332287.93.0.67701681276.issue37221@roundup.psfhosted.org>
In-reply-to
内容
Technically, tp_print was replaced by tp_vectorcall_offset.

But that doesn't answer the question how we should deal with tp_print backwards compatibility. Cython does

FooType.tp_print = 0;

With this in mind, simply replacing tp_print by tp_vectorcall_offset is unsafe as it would break types that actually use vectorcall (there aren't many for now, but who knows how this will change in the future).

It would be safer to replace tp_print by tp_vectorcall since setting that to 0 won't break anything (neither for now, nor when PR 13930 is merged).
历史
日期 用户 动作 参数
2019-06-12 09:38:07jdemeyer修改recipients: + jdemeyer, nascheme, ncoghlan, scoder, vstinner, petr.viktorin, lukasz.langa, serhiy.storchaka, pablogsal
2019-06-12 09:38:07jdemeyer修改messageid: <1560332287.93.0.67701681276.issue37221@roundup.psfhosted.org>
2019-06-12 09:38:07jdemeyer链接issue37221 messages
2019-06-12 09:38:07jdemeyer创建