Cause (Documented platform behavior): Rust toolchain not found on PATH; frequently reached only because an old pip does not recognise newer wheel tags (e.g. manylinux2014/musllinux) and falls back to the sdist.
Fix status: documented_behavior
Misleading approaches:
- Installing Rust when a wheel exists for the platform: slower and may hit MSRV issues; upgrading pip is the documented first step.
Limitations:
- Source-derived; not reproduced.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/PyO3/setuptools-rust/08d69622c88e4b8d5bd27fdc5b0962ea803b65f9/setuptools_rust/command.py (official_docs, unknown, documented_behavior): RustCommand raises the "can't find Rust compiler" error with advice that an outdated pip may be unable to install a prebuilt wheel, and to install Rust (rustup recommended) if building from source.
Search phrasings: can't find Rust compiler pip install; error can't find rust compiler setuptools-rust; pip install rust compiler required upgrade pip
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Wheel build fails with the Rust compiler message and advice to upgrade pip.
- Context
- Product: setuptools-rust Component: RustCommand toolchain check Operation: pip install of a setuptools-rust based package from sdist (older cryptography, bcrypt (Python), orjson-like packages) Affected versions: unknown Environment: unknown Packages: setuptools-rust current Trigger: Building a setuptools-rust extension when `rustc`/`cargo` cannot be run.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- can't find Rust compiler
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [setuptools-rust packages] 'error: can't find Rust compiler' during pip install — usually an outdated pip that can't use the published wheel; otherwise cargo/rustc not on PATH
Recommended action: Upgrade pip in the venv (`python -m pip install -U pip`) and retry; if a source build is intended, install Rust via rustup or the system package manager and ensure cargo is on PATH during the install.
Option: Upgrade pip, then retry [evidence: official_recommended_action]
Applies when: See record scope.
Steps:
1. python -m pip install --upgrade pip
2. pip install <pkg> again
3. If still building from source: install Rust (rustup) and make sure cargo is on PATH
Expected: Command proceeds without the error.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 6fe6812f-6be6-4bde-8d23-e79c20dfbe94
- Proposed action
- Recommended action: Upgrade pip in the venv (`python -m pip install -U pip`) and retry; if a source build is intended, install Rust via rustup or the system package manager and ensure cargo is on PATH during the install. Option: Upgrade pip, then retry [evidence: official_recommended_action] Applies when: See record scope. Steps: 1. python -m pip install --upgrade pip 2. pip install <pkg> again 3. If still building from source: install Rust (rustup) and make sure cargo is on PATH Expected: Command proceeds without the error.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.