Python setup.cfg wrongly applied to all python package dependencies
Metadata
Current evaluation
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.
Suggested action: close stale
Reason: The issue is from the Ubuntu 17.10 era (~8.4 years old) with 0 comments, no labels, and no maintainer engagement. The snapcraft python plugin it describes has since been completely rewritten (modern snapcraft is built on craft-parts), and the referenced snapcraft.yaml source is defunct, so the original problem is no longer applicable to the current codebase.
Impact:
10
Quick Win:
7.0
Staleness:
95
Complexity:
30
Confidence:
70
Support Request:
10
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 |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
10
Quick Win:
7.0
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. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
30
Confidence:
90
Support Request:
10
|
close stale | Reports a build issue where setup.cfg in the working directory incorrectly applies to all Python dependencies during snapcraft builds. Untriaged, inactive for ~8 years, references EOL Ubuntu 17.10. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.