rigetti / rigetti/qcs-sdk-rust
New release request: GLIBC flexibility on qcs_sdk_python (Forschungszentrum Jülich/JSC)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 4
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Description
Dear PyQuil team,
We are contacting you from Forschungszentrum Jülich. We are building your PyQuil software into our Stage/2025. Nonetheless there are only x86_64 and aarch64 manylinux releases with GLIBC 2_28 for qcs_sdk_python (repository not available in GitHub, I open an issue here because it is qcs-sdk-rust). I would like to ask you if it would be possible to make a release of qcs_sdk_python compatible with GLIBC_2_17 as well for x86_64 and aarch64.
Is this possible?
Any additional information you may have I will be glad to provide you so.
Kind regards.
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 inspecting the qcs_sdk_python artifacts listed on PyPI and the qcs-sdk-rust release and packaging entry points that produce the x86_64 and aarch64 manylinux builds. Done means providing qcs_sdk_python releases for both architectures that work with GLIBC_2_17, or documenting why that target cannot be supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100