classic confinement requires manually setting PATH and PYTHONPATH
Metadata
Current evaluation
Classic-confinement snaps built with the python plugin require manually setting PATH and PYTHONPATH via environment: to include $SNAP/bin and $SNAP/lib/python2.7/site-packages; reporter argues snapcraft should do this automatically. No maintainer response or labels; issue is ~9 years old.
Suggested action: close stale
Reason: The issue is 3464 days old with zero comments, no labels, and no maintainer interaction. It references the python plugin and python2.7 site-packages, both of which are long since removed from snapcraft (the python plugin was deprecated/removed in favor of python-common and the project has moved to Python 3), so the specific problem described is no longer reproducible in current versions. The workaround via environment: remains valid, and the underlying concern (automatic PATH/PYTHONPATH injection) is a design decision that would need fresh triage if still relevant.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
21.0
Staleness:
95
Complexity:
40
Confidence:
55
Support Request:
30
|
close stale | Classic-confinement snaps built with the python plugin require manually setting PATH and PYTHONPATH via environment: to include $SNAP/bin and $SNAP/lib/python2.7/site-packages; reporter argues snapcraft should do this automatically. No maintainer response or labels; issue is ~9 years old. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
65
|
close stale | Reporter notes manual PATH and PYTHONPATH setup is needed for classic confinement with the python plugin. Issue has zero comments and no maintainer activity for over 7 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
20
|
close stale | Classic confinement snaps using the python plugin require manual PATH and PYTHONPATH configuration. The issue has been inactive for over 7 years with no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
92
Support Request:
30
|
close stale | Issue reports manual PATH and PYTHONPATH setup needed for classic confinement with the python plugin. Unanswered for over 9 years, likely outdated due to snapcraft evolution. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
15
|
close stale | Classic confinement snaps using the python plugin require manual PATH and PYTHONPATH setup. Open with zero comments, inactive for years, awaiting triage or assignment. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1093 python plugin: do the right thing with classic. | snapcraft | merged | Merged to enable classic confinement for Python snaps by preventing environment variable leaking and using a Python interpreter with classic compilation flags. Resolves LP #1657504 and verified on Trusty. | |
| #1880319 Python plugin --classic snap conflicts with system python | snapcraft (launchpad) | closed | Closed without comments or resolution, likely abandoned. The issue reported a Python plugin conflict where classic confinement snaps incorrectly imported host system libraries instead of packaged dependencies. | |
| #1670388 classic snap are missing some env variables for reaching command name. (snap build, executing it fails) | snapcraft (launchpad) | open | Classic-confinement snapcraft 2.27.1 app wrappers omit $SNAP/bin from PATH, so bare command names fail at runtime and shebangs resolve to system binaries instead of snap ones. Reported 2017, zero comments; later addressed in snapcraft via snapcraft-runner workaround (#2889). |