rigetti / rigetti/rigetti-pyo3
Support for PYPY?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
When building the quil recipe for conda-forge with the pypy implementationthis error occurs:
error[E0432]: unresolved import `rigetti_pyo3::pyo3::types::PyFunction`
--> quil-py/src/program/mod.rs:23:26
|
23 | types::{PyBytes, PyFunction, PyList},
| ^^^^^^^^^^
| |
| no `PyFunction` in `types`
| help: a similar name exists in the module: `PyCFunction`
|
note: found an item that was configured out
--> /home/conda/feedstock_root/build_artifacts/quil-split_1714521268342/_build_env/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.20.3/src/types/mod.rs:26:25
|
26 | pub use self::function::PyFunction;
| ^^^^^^^^^^
For more information about this error, try `rustc --explain E0432`.
error: could not compile `quil-py` (lib) due to 1 previous error
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with quil-py/src/program/mod.rs and the PyO3 0.20.3 error showing that PyFunction is configured out under PyPy. Trace how the quil recipe selects the PyPy implementation and identify the compatibility boundary. Done means the quil recipe builds successfully with PyPy without this unresolved import.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100