rigetti / rigetti/rigetti-pyo3

Spike: investigate switching to PyO3 stub-generation feature

Open
#72 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
11
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Currently this feature is not yet released, but is apparently ready for testing: https://github.com/PyO3/pyo3/issues/5137

Note that if we do not adopt this feature, we should upgrade pyo3-stub-gen, which unfortunately has at least one breaking change since the currently-used version.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading PyO3 issue #5137 to verify the status and behavior of its stub-generation feature, then inspect this repository's current pyo3-stub-gen usage. Done means documenting whether to adopt the PyO3 feature or upgrade pyo3-stub-gen, including the impact of its breaking change.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.