[Python] CUDAQ wheels install things outside its package directory.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 456
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
CUDA Quantum wheels install things outside its package directory in site-packages (or dist-packages).
Apart from the expected cudaq directory, it also installs:
bin/
distributed_interfaces/
include/
lib64/
lib/
src/
targets/
cacert.pem
While, AFAIK, there is not a mandate prohibiting this behavior, doing so, however, goes against best practices and can lead to unexpected errors. Wheels are expected to install packages in a predictable and contained manner. Installing to other locations should be used with caution and only when absolutely necessary, which seems to not be the case here.
All those should be installed within the cudaq directory itself.
Contributor guide
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 Python wheel build and packaging configuration, then compare the installed contents with the listed site-packages paths. The work is done when the wheel places bin, distributed_interfaces, include, lib64, lib, src, targets, and cacert.pem within the cudaq directory without breaking installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100