When installing requirements, pip should avoid using wheels
Metadata
Current evaluation
Fixed in Charmcraft 1.3 by merged PR #541 (commit 0d14d8a2), which disabled binary packages so dependencies are built from source during charm packing.
Resolution: closed resolved
Reason: PR #541 was merged as commit 0d14d8a2, adding pip's --no-binary=:all: behavior for requirements. A maintainer confirmed the fix shipped in Charmcraft 1.3.
Evaluated by: mr-cal-bot
No scores available.
Issue body
This way, if dependencies need to be compiled, they will be compiled in a controlled environment provided for the charm packing.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed in Charmcraft 1.3 by merged PR #541 (commit 0d14d8a2), which disabled binary packages so dependencies are built from source during charm packing. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed in Charmcraft 1.3 by merged PR #541 (commit 0d14d8a2), which builds requirement dependencies locally instead of using wheels. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed in Charmcraft 1.3 by merged PR #541 (commit 0d14d8a2), making requirements installation build dependencies from source instead of using wheels. | |
| stealth/space-bunny-alpha | — | closed resolved | Charmcraft was changed to avoid wheels when installing requirements, keeping compilation in the charm-packing environment. Maintainers confirmed the fix shipped in Charmcraft 1.3. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed in Charmcraft 1.3. The tool now avoids using wheels during requirements installation, ensuring dependencies requiring compilation are built in a controlled environment. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed in Charmcraft 1.3. Pip now avoids wheels during requirements installation, ensuring dependencies compile in the controlled charm packing environment. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed in Charmcraft 1.3. Pip avoids precompiled wheels during requirement installation, forcing dependencies to compile in the controlled charm packing environment. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed in Charmcraft 1.3. Pip now avoids wheels during requirement installation, ensuring dependencies compile in a controlled environment for charm packaging. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#541
(confidence 100%)
Merged as commit 0d14d8a2 and identified by the issue tracker as the fix for issue #342.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #712 Please allow for installing Python dependencies from requirements files using wheels | charmcraft | closed | Maintainers declined wheel-based requirements installs to keep builds controlled and source-tracked, directing binary corner cases to charm-binary-python-packages. | |
| #1664 `charm-python-packages` does not guarantee these packages are installed before packages in `requirements.txt` | charmcraft | closed | Fixed in Charmcraft 3.2 by merged PR #1727 (commit 51a55f73), which installs charm-python-packages before requirements and charm libraries. | |
| #2247 The charm build failed due to the recent release of wheel version 0.46.1. | charmcraft | open | Wheel 0.46.1 broke Charmcraft source-dependency charm builds with a missing bdist_wheel command; pinning 0.45.1 works, but the issue remains untriaged. | |
| #1456 Strict dependencies prevents charm from building | charmcraft | closed | Fixed in PR #1716 (commit def89c50): Charmcraft raised its minimum pip version so strict-dependency builds upgrade old virtual environments first. |