Two python parts in the same snapcraft.yaml result in not installing the python correctly
Metadata
Current evaluation
Stage-time file conflict when two python3 parts share the same interpreter in one snapcraft.yaml (snapcraft 2.14, ~2019). No labels, 0 comments, no maintainer interaction in ~10 years; the old python plugin was later rewritten, so the conflict no longer applies.
Suggested action: close stale
Reason: The issue is ~10 years old (snapcraft 2.14 era) with 0 comments, no labels, and no maintainer interaction, and it describes a known limitation of the legacy python plugin that installed the full interpreter into every part. The related Launchpad bug 1613899 (same two-python-parts conflict) was closed as superseded by updated staging logic, and the python plugin has since been rewritten to use virtualenvs, so the reported conflict is no longer reproducible in current snapcraft. Note: repo code tools were unavailable (no pinned SHA), so the plugin rewrite is based on the related-issue evidence and general project history rather than direct code inspection.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
10.0
Staleness:
95
Complexity:
50
Confidence:
65
Support Request:
50
|
close stale | Stage-time file conflict when two python3 parts share the same interpreter in one snapcraft.yaml (snapcraft 2.14, ~2019). No labels, 0 comments, no maintainer interaction in ~10 years; the old python plugin was later rewritten, so the conflict no longer applies. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
92
Support Request:
85
|
close stale | Build fails due to path conflicts when using multiple python3 parts in snapcraft v2.14. User seeks a way to avoid shared Python file conflicts between parts. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
85
|
close stale | Build fails due to file conflicts between two python3 parts in Snapcraft 2.14. Issue is nearly 10 years old and references an obsolete tool version no longer supported. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
60
|
close stale | Snapcraft build fails due to file path conflicts between two python3 parts. No maintainer response or labels; issue is nearly 10 years old and uses obsolete snapcraft 2.14. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
35
Confidence:
92
Support Request:
75
|
close stale | Multiple python3 parts in a single snapcraft.yaml cause staging conflicts from overlapping standard library and pip paths. The issue remains open, unassigned, and lacks comments, awaiting triage. |
Update history
No update history recorded yet.
Related work
-
Duplicate Of:
snapcraft (launchpad)#1613899
(confidence 70%)
Same reported symptom: two python parts with common dependencies produce file-path conflicts with different contents; that bug was closed without resolution as superseded by updated staging logic.
Related issues
No related issues found above the similarity threshold.