python plugin v2 doesn't quote python-packages
Metadata
Current evaluation
Closed without resolution or comments. The python plugin v2 fails to quote python-packages entries, causing pip install failures with spaces and platform markers. The issue appears abandoned.
Suggested action: —
No scores available.
Issue body
The v2 python pluging doesn't quote entries from python-packages when passing them to pip.
The following works when based on core18 but not with core20:
python-packages:
- ibm-db-sa; platform_machine == 'x86_64'
- ibm-db-sa; platform_machine == 'ppc64le'
- ibm-db-sa; platform_machine == 's390x'
Looking at the resulting build.sh script in the build environment, the "pip install" commands doesn't quote individual entries, so spaces cause issue.
Note that just removing spaces doesn't fix the issue, as platform_machine values need to be quoted, and quotes get lost in the script.
Manually double-quoting each entry in the script makes it work.
This is with snapcraft 4.0.5 (4892)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The python plugin v2 fails to quote python-packages entries, causing pip install failures with spaces and platform markers. The issue appears abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The python plugin v2 failed to quote python-packages entries for pip, causing build script failures. Likely abandoned or superseded by newer snapcraft versions. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1702 Python plugin v2 passes shell-quoted python-packages as literal pip arguments | craft-parts | closed | Closed and linked to internal Jira ticket CRAFT-5286. No code fix or merge was documented. The reported shell quoting bug remains unaddressed. | |
| #1616032 python2 plugin expects pip to be called pip2 | snapcraft (launchpad) | closed | The python2 plugin fails when pip is not named pip2. The report was abandoned and closed without resolution or fix, due to zero comments and inactivity. |