rigetti / rigetti/qcs-sdk-rust
`qcs-sdk-python` should take over the `qcs` PyPI package
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 4
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Description
We own the qcs package on PyPI, but don't use it for anything useful. The package is easily mistaken for qcs-sdk-python since the Rust library is itself called qcs. We should repurpose the qcs package as a home for qcs-sdk-python.
One future issue: qcs currently has one release, 2.1.0. PyPI doesn't let you replace the package behind a version, even if you delete it. This means we'll run into an issue uploading the package to PyPI if the QCS library ever reaches 2.1.0.
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 by reviewing the qcs-sdk-python packaging and publishing configuration, then inspect the linked qcs PyPI release history. Determine how the package can be repurposed without colliding with the existing 2.1.0 release; done means a documented, workable path for publishing qcs-sdk-python as qcs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100