Python libraries installed by python path are not found in sys.path
Metadata
Current evaluation
Core20 destructive builds could package a host virtualenv's bin/python3, hiding snap site-packages; the cause and PATH workaround were identified, but core20 support has since been removed.
Suggested action: close stale
Reason: The reporter and maintainer isolated the failure to a host virtualenv selected during --destructive-mode and confirmed that running with PATH=/usr/bin:$PATH fixes it. Commit fa7952b4d and PR snapcraft#6019 removed core20 support, so the affected base is no longer part of current Snapcraft and this report is demonstrably obsolete.
Evaluated by: mr-cal-bot
Impact:
8
Quick Win:
3
Complexity:
40
Confidence:
98
Actionability:
72
Issue body
snapcraft 4.0, on a core20 snap
Python libraries and apps installed by a python part (via pip or setup.pyt dependencies) are installed in $SNAP/lib/python3.8/site-packages, but the path is not added to sys.path:
sys.path = [
'/',
'/usr/lib/python38.zip',
'/usr/lib/python3.8',
'/usr/lib/python3.8/lib-dynload',
'/usr/lib/python3/dist-packages',
]
As such, those modules are not found when running the app.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
8
Quick Win:
3
Complexity:
40
Confidence:
98
Actionability:
72
|
close stale | Core20 destructive builds could package a host virtualenv's bin/python3, hiding snap site-packages; the cause and PATH workaround were identified, but core20 support has since been removed. | |
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
8
Complexity:
50
Confidence:
96
Actionability:
55
|
close stale | Legacy core20 Python-plugin builds could select a host virtualenv and omit snap site-packages from sys.path. PATH=/usr/bin fixes it; core20 support was later removed. | |
| qwen/qwen3.6-35b-a3b |
Impact:
70
Quick Win:
34
Complexity:
30
Confidence:
60
Actionability:
70
|
needs triage | Python packages installed by python part in $SNAP/lib/pythonX.Y/site-packages are not accessible because the path is missing from sys.path. Issue is open with no maintainer response or labels. | |
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
20
Staleness:
90
Complexity:
55
Confidence:
55
Support Request:
25
|
needs triage | Snapcraft 4.0 core20: Python parts install packages to $SNAP/lib/python3.8/site-packages but that path is missing from sys.path, so apps cannot import them. No labels, no comments, no maintainer response; last activity ~6.3 years ago. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
20
|
close stale | Python libraries installed via snapcraft's python part are not accessible because the site-packages path is missing from sys.path. Issue is over six years old with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Python packages installed via pip in snapcraft 4.0/core20 are not added to sys.path, causing import failures. The report is over six years old with zero maintainer engagement and likely pertains to deprecated core20/snapcraft versions. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
20
|
close stale | Reports Python site-packages not being added to sys.path in snapcraft 4.0 on core20. Issue is 6 years old with no maintainer response or comments. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Superseded By:
snapcraft#6019
(confidence 99%)
PR #6019, implemented by commit fa7952b4d, dropped core20 support.
Related issues
No related issues found above the similarity threshold.