Python plugin --classic snap conflicts with system python
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
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.
Suggested action: —
No scores available.
Issue body
Using a published `confinement: classic` snap using `plugin: python`, multiple people seem to have reported the snap trying to use/`import` host libraries rather than the dependencies installed during the snap plugin's build stage.
Errors:
https://github.com/iterative/dvc/issues/3514
Snapcraft config:
https://github.com/iterative/dvc/blob/master/snap/snapcraft.yaml
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and closed without resolution. Classic Python snaps incorrectly imported host system libraries instead of snap-built dependencies, causing runtime conflicts. No fix was implemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Classic snaps using the Python plugin incorrectly imported host system libraries instead of snap-built dependencies. The report was closed without comments or resolution, indicating it was abandoned. |
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. | |
| #5407 Unable to build Python snaps using classic confinement with core24 using snapcraft 8.8.0 (8.x/stable) | snapcraft | closed | Resolved as a configuration issue. Classic Python snaps on core24 require explicitly adding python3.12-minimal to stage-packages and adjusting the app command. The developer acknowledged documentation gaps and announced upcoming Python plugin improvements. | |
| #1860884 Python plugin: paths for from the snapcraft snap in sys.path break dependencies | snapcraft (launchpad) | closed | Abandoned due to inactivity. The Python plugin incorrectly included snapcraft snap paths in sys.path during builds, causing dependency conflicts. No resolution or fix was implemented. | |
| #1670749 classic confinement requires manually setting PATH and PYTHONPATH | snapcraft (launchpad) | open | 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. | |
| #1882994 [4.0.4][strict] usage of the python plugin forces the python3 interpreter to be shipped in the snap | snapcraft (launchpad) | closed | Closed without resolution. The python plugin forces python3 into the snap, causing runtime path conflicts. Likely abandoned or superseded by newer snapcraft plugin versions. | |
| #1696127 Bad sys.path for classic Python2 | snapcraft (launchpad) | closed | Classic Python 2 snaps incorrectly prioritize system and user local paths in sys.path, causing package shadowing. The report was closed without comments or a fix, indicating it was abandoned. |