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 nascheme, serhiy.storchaka, steve.dower, vstinner
Date 2020-02-08.14:28:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1581172130.47.0.502264409075.issue39573@roundup.psfhosted.org>
In-reply-to
Content
> "static inline" functions are not opaque

I'm well aware of that :-) But once the CPython code base will stop accessing directly PyObject fields directly, it would become possible to experiment changing PyObject layout, at least testing it in CPython.

First changes are just to prepare the code base to experiment the real change. But as Serhiy pointed out, the second part will have an impact on performance and so should be carefully benchmarked to balance advantages and drawbacks, even if it's only done in the limited C API.
History
Date User Action Args
2020-02-08 14:28:50vstinnersetrecipients: + vstinner, nascheme, serhiy.storchaka, steve.dower
2020-02-08 14:28:50vstinnersetmessageid: <1581172130.47.0.502264409075.issue39573@roundup.psfhosted.org>
2020-02-08 14:28:50vstinnerlinkissue39573 messages
2020-02-08 14:28:50vstinnercreate