Can't have two python3 parts using setuptools
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without resolution or comments. The build conflict report was likely abandoned or superseded by upstream changes to snapcraft and Python packaging standards over the past decade.
Suggested action: —
No scores available.
Issue body
If two python3 parts use setuptools, building a snap will fail since some common files have different contents:
Error: parts treac and pysmbus have the following file paths in common which have different contents:
usr/lib/python3/dist-packages/easy-install.pth
usr/lib/python3/dist-packages/pip-7.1.2-py3.4.egg/EGG-INFO/entry_points.txt
usr/lib/python3/dist-packages/pysmbus-0.1.egg-info/SOURCES.txt
The latter two are intermittent. They don't always conflict. But the first one will always conflict.
An example of a snapcraft.yaml that produces this error:
name: treac
version: 0
vendor: Bjorn Tillenius <email address hidden>
binaries:
treacd:
exec: usr/bin/treac
summary: TREAC - The Treadmill Controller
description: Provides an API for controlling a treadmill on a Raspberry Pi
icon: icon.png
parts:
treac:
plugin: python3
source: git://github.com/bjornt/treac
pysmbus:
plugin: python3
source: git://github.com/bjornt/pysmbus
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The build conflict report was likely abandoned or superseded by upstream changes to snapcraft and Python packaging standards over the past decade. | |
| qwen/qwen3.6-35b-a3b | — | — | Build failures from conflicting setuptools files in multiple python3 parts were not addressed. The report was closed without a fix or workaround, effectively abandoned due to age. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. Multiple python3 parts using setuptools cause snapcraft build failures due to dist-packages file conflicts. No comments or fixes were implemented. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1613899 Two python parts have common dependencies file conflicts occur | snapcraft (launchpad) | closed | Closed without resolution or comments. The file conflict error when multiple Python parts share common dependencies was abandoned, likely superseded by updated Snapcraft staging logic. | |
| #1794443 Python parts can't be automatically rebuilt if dirty | snapcraft (launchpad) | closed | Closed without comments or documented resolution. The snapcraft build caching bug preventing dirty Python parts from rebuilding due to missing python3 paths was abandoned. | |
| #1778716 snapcraft clean snapcraft fails as it cannot find python | snapcraft (launchpad) | closed | Closed without comments or explicit resolution, likely abandoned or resolved in a later release. The bug reported a MissingPythonCommandError during snapcraft clean due to python3 path resolution ordering. | |
| #1617907 Two python parts in the same snapcraft.yaml result in not installing the python correctly | snapcraft (launchpad) | open | 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. | |
| #1507357 Fail to build snap python3 distutils project | snapcraft (launchpad) | closed | Closed without resolution. The snap build failure for Python3 distutils projects, caused by a missing usr/bin/python3 path, appears abandoned due to zero comments and extended inactivity. | |
| #1511440 python based package created using snapcraft fails review checks due to external symlink | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft-built Python2 packages failed store review checks due to external symlinks. The report received no comments or fixes and was abandoned. | |
| #1498212 setup.py based projects from remote sources broken | snapcraft (launchpad) | closed | Remote setup.py projects failing during snapcraft builds were closed without resolution. Zero comments and no linked fixes indicate the report was abandoned due to prolonged inactivity. | |
| #1587193 build of python3 snap fails with 'error: option --single-version-externally-managed not recognized' | snapcraft (launchpad) | closed | Closed without resolution. The snapcraft pip flag compatibility issue was abandoned due to inactivity and likely superseded by updated snapcraft and pip versions. | |
| #1680538 It's not possible to depend on a python package build by a different part | snapcraft (launchpad) | closed | Closed without resolution. The cross-part Python package dependency limitation was abandoned, leaving the $SNAPCRAFT_STAGE path workaround as the only available solution. | |
| #1808782 Python snap that checks for 3.x at build time fails | snapcraft (launchpad) | closed | Closed without resolution. The report detailed a Python snap build failure caused by a version check mismatch, but received no comments or fixes, indicating the issue was abandoned. |