RosettaCommons / RosettaCommons/foundry
No matching distribution found for cuequivariance-ops-cu12>=0.5.0; sys_platform == "linux"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 966
- Forks
- 181
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 2
Description
Hi, I encountered the following error during installation. Could you please advise me on how to resolve it?
pip install -e .
Obtaining file:///share/home/mark/software/modelforge
Installing build dependencies ... done
Checking if build backend supports build_editable ... done
Getting requirements to build editable ... done
Installing backend dependencies ... done
Preparing editable metadata (pyproject.toml) ... done
Collecting atomworks==1.0.0 (from rf3==0.1.dev908+g5c8ba5f2a)
Using cached atomworks-1.0.0-py3-none-any.whl.metadata (9.0 kB)
Collecting beartype<1,>=0.18.0 (from rf3==0.1.dev908+g5c8ba5f2a)
Using cached beartype-0.21.0-py3-none-any.whl.metadata (33 kB)
INFO: pip is looking at multiple versions of rf3 to determine which version is compatible with other requirements. This could take a while.
ERROR: Could not find a version that satisfies the requirement cuequivariance-ops-cu12>=0.5.0; sys_platform == "linux" (from rf3) (from versions: none)
ERROR: No matching distribution found for cuequivariance-ops-cu12>=0.5.0; sys_platform == "linux"
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 with the reported pip install -e . flow and inspect pyproject.toml, especially the dependency declaration for cuequivariance-ops-cu12>=0.5.0; sys_platform == "linux". Reproduce the missing-distribution error in a Linux environment and verify that the project’s editable installation completes successfully with a resolvable dependency.
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
- Needs clarification
- Newbie friendliness
- 30/100