when two python3 parts are used the pycs give a conflict
Metadata
Current evaluation
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.
Resolution: closed resolved
Reason: Commit 459c64e88, “Explicitly ignore __pycache__,” addresses the overlapping PYC files responsible for staging conflicts. PR #109 stated that the bug was already fixed but its regression test was not merged due to resource-handling issues.
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.
Launchpad Details: [#LP1502105](https://bugs.launchpad.net/bugs/1502105) maarten ectors - 2015-10-02 08:54:28 -0300
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | 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. | |
| stealth/space-bunny-alpha | — | closed stale | The staging conflict was closed without a recorded fix; a later commit, 459c64e88, explicitly ignored __pycache__ PYC files. | |
| 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 | — | — | Closed without resolution. The report described PYC file conflicts during the stage step when using multiple Python 3 parts. No fix or workaround was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The PYC file conflict when staging multiple Python 3 parts was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without documented resolution. The report described PYC file conflicts during staging when multiple Python 3 parts were used. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution or comments. The PYC file conflict during multi-part Python 3 staging was not addressed, indicating the report was abandoned or superseded by newer versions. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#109
(confidence 100%)
Regression-test PR for LP#1502105; closed unmerged because the bug was fixed and the test introduced resource problems.
-
Likely Fixed By:
canonical/snapcraft@459c64e88
(confidence 90%)
The commit explicitly excludes __pycache__, matching the reported PYC conflict.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1502105 when two python3 parts are used the pycs give a conflict | snapcraft (launchpad) | closed | 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. |