when two python3 parts are used the pycs give a conflict
Metadata
Current evaluation
Overlapping Python 3 .pyc staging conflicts were fixed in ubuntu-core/snapcraft#50 using Python-plugin snap_fileset filtering; regression coverage was proposed in #109.
Resolution: closed resolved
Reason: Resolved by ubuntu-core/snapcraft#50. The reporter confirmed that staging conflicts occurred without the Python plugin's snap_fileset filtering.
Evaluated by: mr-cal-bot
No scores available.
Issue body
When two python3 parts are used then the PYC files give a conflict in the stage step.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Overlapping Python 3 .pyc staging conflicts were fixed in ubuntu-core/snapcraft#50 using Python-plugin snap_fileset filtering; regression coverage was proposed in #109. | |
| stealth/space-bunny-alpha | — | closed resolved | Overlapping .pyc files caused staging conflicts between Python 3 parts; PR #50 was reported to fix the issue, while regression-test PR #109 was closed unmerged. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a recorded fix; the report of staging conflicts between .pyc files from two Python 3 parts was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | PYC file conflicts during the stage step when using two Python 3 parts were reported but closed without resolution. No comments, fixes, or pull requests were submitted, leaving the report abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The PYC file conflict during the stage step when using multiple python3 parts remains unfixed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The reported PYC file conflict during the stage step when using multiple python3 parts remains unfixed. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
ubuntu-core/snapcraft#50
(confidence 100%)
The fix PR was explicitly cited as resolving the Python .pyc conflict.
-
Duplicate Of:
ubuntu-core/snapcraft#8
(confidence 100%)
The Launchpad report was moved to this GitHub issue.
-
Related To:
ubuntu-core/snapcraft#109
(confidence 100%)
Proposed a separate regression test for the fixed behavior but was closed unmerged.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #8 when two python3 parts are used the pycs give a conflict | snapcraft | closed | Resolved by explicitly ignoring __pycache__ in commit 459c64e88; regression-test PR #109 was closed unmerged after the fix because the test caused resource-handling problems. | |
| #1850921 Python plugin: file conflicts when using the plugin with a custom version of Python from another part | snapcraft (launchpad) | open | Python plugin reportedly provisions Python 3.5 before a custom-Python part is staged, causing /usr/bin conflicts; this Snapcraft 2.44 report remains untriaged against the current plugin architecture. | |
| #1617907 Two python parts in the same snapcraft.yaml result in not installing the python correctly | snapcraft (launchpad) | open | Snapcraft 2.14 fails when multiple Python parts stage conflicting interpreter files. Similarity to resolved bug #1531570 was disputed, and the old report remains unverified. | |
| #1663739 it's not possible to have two python parts | snapcraft (launchpad) | closed | Fixed by merging snapcraft#1138 in commit 73604a1f0, excluding Python RECORD files so multiple Python parts no longer conflict during staging. |