pyo3
pyo3 copied to clipboard
Rust bindings for the Python interpreter
https://peps.python.org/pep-0489/ This is very much WIP, opening for discussion, previously: https://github.com/PyO3/pyo3/discussions/1982
It would be an interesting feature to be able to export traits from Rust to Python, perhaps with a `#[pytrait]` macro, or with some modification to `#[pyclass]`. I think this...
I tried the official example- [https://pyo3.rs/v0.16.2/trait_bounds.html](url). It works well when the code is in `.py` file, I can see the print from python and rust. But when I use it...
### Bug Description Any methods implemented on #[pyclass] structs that attempt to take ownership and move `self` produce type mismatch errors ### Steps to Reproduce 1. Create #[pyclass] in module...
https://github.com/nextest-rs/nextest Try it out to see if it can help speeding up CI runs.
TLDR; I propose a `#[pyo3(signature)]` attribute for both `#[pyfunction]` and `#[pymethods]` which: - automatically generates `text_signature` - leaves no room for ambiguity - is required to specify default arguments (including...
Fixes #1084 Fixes #771 Fixes #341 Fixes #340
As part of our project, we embed Python code in Rust workers using PyO3 (see [this project](https://github.com/media-cloud-ai/mcai_worker_sdk/tree/master/py_mcai_worker_sdk)). Although the binding is really working well, we lack the Python to Rust...
### Bug Description Some code within a `pyfunction` is panicing, but rather than this resulting in a `PyException` via #797, it leads to a SIGABRT. A related issue was previously...
I believe Rust 1.60 (due in six weeks' time) will contain a stabilised `-C instrument-coverage` flag to support the coverage for which we currently use nightly. It might be interesting...