python console_scripts not installed into /snap/<snap>/current/bin
Metadata
Current evaluation
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.
Resolution: closed resolved
Reason: Reporter corey.bryant confirmed the fix worked after snapcore/snapcraft#1202 (commit dbdaf36a4, 'python plugin: support pbr/setup.cfg projects'), which switched from `pip install` to invoking `setup.py`, restoring console_scripts/wsgi_scripts into $SNAP/bin. Regression had been introduced by snapcore/snapcraft#1093 (commit e7824093f), which changed runnable to the python -m pip command list.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | 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. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed the Python plugin regression in snapcore/snapcraft#1202 (commit dbdaf36a4), restoring console_scripts and wsgi_scripts installation for pbr/setup.cfg projects. | |
| stealth/space-bunny-alpha | — | closed resolved | Regression in python plugin stopped generating console_scripts for pbr projects. Fixed by merged PR #1202 (commit dbdaf36a4), which runs setup.py install to generate entry-point scripts; reporter confirmed bin files appear. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a documented fix after nearly nine years of inactivity; the reported Python entry-point script installation regression was not resolved. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without documented resolution. Likely abandoned due to age and zero comments. The snapcraft regression blocking Python console_scripts installation into /snap/<snap>/current/bin remains unresolved. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The snapcraft regression preventing Python console_scripts and wsgi_scripts from installing to /snap/<snap>/current/bin remains unresolved. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#1202
(confidence 99%)
Fix PR by sergiusens, merged as commit dbdaf36a4 'python plugin: support pbr/setup.cfg projects'; reporter confirmed bins installed.
-
Caused By:
snapcore/snapcraft#1093
(confidence 95%)
Identified by elopio as the source of the regression (commit e7824093f changing runnable to the python -m pip list).
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1734213 Python scripts named pip* filtered out of snaps | snapcraft (launchpad) | closed | Fixed the Python plugin's overbroad -bin/pip* filter in snapcraft#1763 (commit a1fb1aeac), allowing pip2pi console scripts to reach the stage. | |
| #1841861 Python plugins fails to build a snap when some parts depends on unpublished modules | snapcraft (launchpad) | closed | Fixed by PR #2771 (commit 9bac0fd64), which made the Python plugin try processing setup.py before querying PyPI, allowing parts to use locally built packages. |