Add minimal C-api implementation that builds with Pyo3#7562
Add minimal C-api implementation that builds with Pyo3#7562bschoenmaeckers wants to merge 160 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Could you try with hpy if you dont mind? We are looking for sustainable way |
That would require significant changes in codebase that are using the CPython api spec. I would like to explore the possibility to use the ab3/abi3t api. Would you be willing to accept that? |
youknowone
left a comment
There was a problem hiding this comment.
This way will not work.
Just in case, the code can be generated, but I hope we carefully review the decisions. unlikely-to-happen decisions must be reviewed and justified by document(comment) the decisions.
If you are not familiar enough to the project to decide good way, please start from a smaller and simpler issue.
We only need abi3t, because we are compatible to free-threading.
We have to minimize the surface of C API. if HPy helps it, we need HPy.
Ideally c api must be very thin wrappers to RustPython features. "code" must not be included in this crate.
I wanted to create as little of modificaties to the existing code base without significant motivation. But I definitely agree with you. |
| pyo3 = { workspace = true, features = ["auto-initialize", "abi3"] } | ||
|
|
||
| [features] | ||
| # Enable PyObject_CallMethodObjArgs variadic function, which is only available on nightly Rust. |
There was a problem hiding this comment.
| # Enable PyObject_CallMethodObjArgs variadic function, which is only available on nightly Rust. | |
| # Enable PyObject_CallMethodObjArgs variadic function, which is only available on nightly Rust. | |
| # TODO: remove this when the `c_variadic` feature is stabilized (https://github.com/rust-lang/rust/issues/44930) |
There was a problem hiding this comment.
As this will be stabilised very soon. I was planning to removing this feature entirely before merging this.
|
@youknowone Small update on the current process: The basic API surface has now been implemented and merged. This allows us to implement and run tests for the most commonly used Python types and functions. What remains is the implementation of the less commonly used abi3 functions, along with module and type creation support. The former should be relatively straightforward and can be implemented by me, someone else, or even an AI agent. The latter is more challenging. Current TODO list of unimplemented C API functions in PyO3Click here for the full list of straightforward TODO functionsUnimplemented C API functionsMapping source:
|
|
@JamesClarke7283 would you like to take the straight-forward abi3 functions using AI? |
This is my shot at implementing a minimal Cpython compatible C-api. I've implemented the bare minimum to get the included Pyo3 example running where most of the api is stubbed. I'm not familiar with the rest of the RustPython code base so let me know what you think and where I did stupid things.
Please take extra care reviewing the pylifecycle.rs & pystate.rs files where I try to setup the RustPython interpreter.
xref #5604