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, vstinner
Date 2020-02-07.01:42:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1581039736.63.0.148591907181.issue39573@roundup.psfhosted.org>
In-reply-to
Content
Make PyObject an opaque structure is also a first step towards the more ambitious project "HPy" project which is fully opaque:
https://github.com/pyhandle/hpy

This API is written from scratch and currently implemented on top on the existing C API.

The following article is a nice introduction to the overall idea:
https://morepypy.blogspot.com/2019/12/hpy-kick-off-sprint-report.html

From my point of view, the long term goal would be to get better performance on PyPy and having a single API for C extension which would be efficient on all Python implementations (not only CPython).

Currently, the C API is not only a performance issue to run C extensions on PyPy. It's also an issue in CPython. Because the C API leaks too many implementation details, we cannot experiment optimizations.

See also: https://pythoncapi.readthedocs.io/rationale.html
History
Date User Action Args
2020-02-07 01:42:16vstinnersetrecipients: + vstinner, nascheme
2020-02-07 01:42:16vstinnersetmessageid: <1581039736.63.0.148591907181.issue39573@roundup.psfhosted.org>
2020-02-07 01:42:16vstinnerlinkissue39573 messages
2020-02-07 01:42:16vstinnercreate