Python setup.cfg wrongly applied to all python package dependencies
Metadata
Current evaluation
An old Python-plugin report says a part's setup.cfg affects pip dependency installation and breaks builds; it remains open, untriaged, and needs verification on current Snapcraft.
Suggested action: needs triage
Reason: The issue has no labels or substantive maintainer response; its sole 2018 comment contains no assessment, and the reproducer references a defunct Launchpad source without including the actual error. Current Snapcraft still invokes pip from the part build directory without an isolation flag, so the behavior should be reproduced against the current craft-parts-based plugin before determining whether it is fixed.
Evaluated by: mr-cal-bot
Impact:
40
Quick Win:
8
Complexity:
55
Confidence:
84
Actionability:
46
Issue body
This is just a report of the problem discussed in [1] which I think is still present (or something similar).
The problem is that for rapid-photo-downloader, the cwd during build holds a setup.cfg, which then gets applied to all python installs during build.
I created a (stupid?) adaptation of the author's defunct snapcraft.yaml from [2] which I put at [3].
On a clean digital-ocean applet (Ubuntu 17.10 server) a "snapcraft" call (both with current HEAD and with current "snap install snapcraft --classic" results in an error while installing the first python package, in this case pip:
[1] https://forum.snapcraft.io/t/python-setup-cfg-wrongly-applied-to-all-python-package-dependencies/1097
[2] http://bazaar.launchpad.net/~dlynch3/rapid/zeromq_pyqt/view/head:/snap/snapcraft.yaml
[3] https://gist.github.com/black-puppydog/90de8778b4006ed89196992e7d800271
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
8
Complexity:
55
Confidence:
84
Actionability:
46
|
needs triage | An old Python-plugin report says a part's setup.cfg affects pip dependency installation and breaks builds; it remains open, untriaged, and needs verification on current Snapcraft. | |
| stealth/space-bunny-alpha |
Impact:
58
Quick Win:
11
Complexity:
47
Confidence:
61
Actionability:
36
|
needs triage | Reported Python plugin bug where a source-tree setup.cfg affects dependency installation; the old reproducer lacks logs or confirmation that the behavior remains | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
12
Complexity:
50
Confidence:
60
Actionability:
60
|
needs triage | Python plugin applies setup.cfg from cwd to all python package dependencies during build, causing build failures | |
| qwen/qwen3.8-27b |
Impact:
10
Quick Win:
7
Staleness:
95
Complexity:
30
Confidence:
70
Support Request:
10
|
close stale | 2017 report that a setup.cfg in the build directory was applied to all pip installs. No comments, no labels, no maintainer response. The python plugin has since been fully rewritten, so the problem is almost certainly no longer reproducible. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Reports a build bug where a local setup.cfg incorrectly applies to all Python dependencies during snapcraft builds. Unlabeled, no comments, inactive for over 8 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
90
Support Request:
10
|
close stale | Bug report describing how setup.cfg in the build directory incorrectly applies to Python dependencies during snapcraft builds. No maintainer response, references EOL Ubuntu 17.10, and lacks current relevance. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
close stale | Reports a snapcraft build bug where a local setup.cfg incorrectly applies to all Python dependencies. The issue is 8 years old, references deprecated Ubuntu 17.10, and has zero maintainer engagement or labels. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.