Python scripts named pip* filtered out of snaps
Metadata
Current evaluation
Fixed the Python plugin's overbroad -bin/pip* filter in snapcraft#1763 (commit a1fb1aeac), allowing pip2pi console scripts to reach the stage.
Resolution: closed resolved
Reason: Merged PR snapcraft#1763 introduced finer-grained file filters for pip, resolving the accidental exclusion of console scripts whose names begin with "pip".
Evaluated by: mr-cal-bot
No scores available.
Issue body
The PyPI package pip2pi installs a number of scripts beginning with pip. When building a snap where I want these available, they don't make it through the stage step.
It looks like the problem is the `fileset.append('-bin/pip*')` in PythonPlugin.snap_fileset.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed the Python plugin's overbroad -bin/pip* filter in snapcraft#1763 (commit a1fb1aeac), allowing pip2pi console scripts to reach the stage. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed pip-prefixed Python scripts being excluded during staging by replacing the broad pip* filter with finer-grained filters in PR #1763 (commit a1fb1aeac). | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without discussion. The restrictive pip* fileset filter in PythonPlugin.snap_fileset was removed, resolving the issue and allowing pip-prefixed scripts to be included in snaps. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. Python scripts prefixed with pip were incorrectly filtered from snaps due to a hardcoded exclusion in PythonPlugin.snap_fileset. No fix or resolution was documented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments, likely abandoned due to inactivity. The reported bug regarding PythonPlugin.snap_fileset filtering pip* scripts during snap builds remains unresolved. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution after identifying a fileset exclusion in PythonPlugin.snap_fileset that filtered pip* scripts from snaps. No fix was implemented. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/snapcraft#1763
(confidence 99%)
Commit a1fb1aeac from PR #1763 directly updates the Python plugin's pip-related file filters.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1616032 python2 plugin expects pip to be called pip2 | snapcraft (launchpad) | closed | Fixed the Python 2 plugin's incorrect pip2 invocation in snapcraft PR #771 (commit bb7bd40e1); the fix was released in Snapcraft 2.17. | |
| #1670852 python console_scripts not installed into /snap/<snap>/current/bin | snapcraft (launchpad) | closed | Fixed: regression in python plugin (from PR #1093 / commit e7824093f) where pip installed pbr/setup.cfg projects but skipped entry points. Fixed by PR #1202, commit dbdaf36a4, which runs setup.py instead of pip install. | |
| #1621540 do not compile with pip | snapcraft (launchpad) | closed | Fixed in snapcore/snapcraft#779 (commit b9e1aabf6): the Python plugin now skips pip compilation of .pyc files, which were removed later anyway. |