Swig isn't executed with snapcraft python plugin
Metadata
Current evaluation
Legacy Python 2/SWIG reproducer from 2016 lacks the generated sequencer_alsa.py; the affected toolchain is retired and the modern plugin no longer uses pip --no-compile.
Suggested action: close stale
Reason: The report explicitly targets python-version: python2 and a 2016 package archive, and its sole comment is an automated public-bug notice with no maintainer assessment. Craft-parts commit a80f9c26 moved Python compatibility to 3.10, while the current Python plugin no longer passes --no-compile, so the exact affected toolchain is retired and this report is obsolete.
Evaluated by: mr-cal-bot
Impact:
24
Quick Win:
3
Complexity:
61
Confidence:
86
Actionability:
31
Issue body
1. Use a project having a swift module:
requirements.txt:
https://github.com/didrocks/python-midi/archive/v0.2.3+2016.11.tar.gz
2. Use the python plugin in your snapcraft.yaml:
parts:
foo:
source: .
plugin: python
python-version: python2
requirements: requirements.txt
build-packages: [swig3.0]
After snapcrafting this parts (not a cleanbuild, so swig is available on the system), you will notice that the .so file is compiled:
parts/foo/install/lib/python2.7/site-packages/midi/sequencer/_sequencer_alsa.so
But you don't have the binding generated by swift, "sequencer_alsa.py".
On the same machine, I can create a virtualenv and then get the module compiles:
$ virtualenv venv
$ . venv/bin/active
$ pip install --r requirements.txt
-> venv/lib/python2.7/site-packages/midi/sequencer/sequencer_alsa.py was generated
As a quick try, I tried removing "--no-compile" in pip_install() in the python plugin, without success. Nothing in the verbose pip outputs explains why swig isn't ran.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
24
Quick Win:
3
Complexity:
61
Confidence:
86
Actionability:
31
|
close stale | Legacy Python 2/SWIG reproducer from 2016 lacks the generated sequencer_alsa.py; the affected toolchain is retired and the modern plugin no longer uses pip --no-compile. | |
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
2
Complexity:
82
Confidence:
92
Actionability:
30
|
close stale | A Python 2-era Snapcraft plugin built a SWIG extension but omitted its generated Python wrapper; this affected legacy workflow no longer exists in the current plugin. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
5
Complexity:
60
Confidence:
50
Actionability:
40
|
needs triage | SWIG bindings not generated when using snapcraft python plugin with pip install. Issue is 9.8 years old, no labels or maintainer response. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
10
Staleness:
95
Complexity:
30
Confidence:
82
Support Request:
15
|
close stale | Snapcraft python plugin (2016) fails to run swig during pip install, so generated .py bindings are missing from the built snap. No maintainer response in ~10 years; references python2 and swig3.0, both EOL. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
15
|
close stale | Python plugin fails to execute SWIG during build, missing generated binding files. Untriaged, inactive for ~9.6 years, likely obsolete due to Python 2 deprecation and project age. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
100
Complexity:
25
Confidence:
90
Support Request:
30
|
close stale | Reports swig not executing when building Python packages with snapcraft's python plugin. Unlabelled, no maintainer response, and over 9 years old with Python 2 references. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
100
Complexity:
50
Confidence:
90
Support Request:
10
|
close stale | Bug report stating SWIG bindings aren't generated when using the snapcraft python plugin. No maintainer response or activity in nearly 10 years. Likely obsolete due to major plugin and Python version changes. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft#779
(confidence 86%)
PR #779 introduced --no-compile for pip installs, the exact option the reporter tested; it is relevant context but not a confirmed fix.
Related issues
No related issues found above the similarity threshold.