[FR] Move `.config.` (`setup.cfg` parser) into a separate package and vendorize it
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system
Research direction
Locate the built-in setuptools submodule responsible for parsing setup.cfg and trace how it is used. Define the separate package boundary and its integration points, then verify that setuptools vendorizes it while external tools can continue reading setup.cfg metadata.
Written by the indexing model from the issue text.
Description
What's the problem this feature will solve?
Even though setup.cfg files are deprecated and their support gonna be removed somewhen, it is here to stay, there are enough packages using it. So there is a need to read these files. Unfortunately they cannot be read properly by generic configparser (at least without additional postprocessing). So an out-of-the-box solution is needed.
Describe the solution you'd like
The library parsing setup.cfg is splitted into a separate package, that can be used by tools that have to deal with setup.cfg even after setuptools drops support of this metadata format.
setuptools eliminates the built-in submodule and instead vendorizes that package.
Alternative Solutions
Not to drop support of setup.cfg.
Additional context
No response
Code of Conduct
- I agree to follow the PSF Code of Conduct
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pypa/setuptools
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pypa/setuptools#5272 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
pypa/setuptools#5235 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pypa/setuptools#5234 · 1 comment ·
-
bug Needs Triage
Difficulty 1/5 Under an hour Newbie friendliness 78/100
pypa/setuptools#4135 · 1 comment · 1 reaction ·
-
documentation Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
pypa/setuptools#2753 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100