expose structured package data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Package metadata is standardized and structured data that is often reused across projects, (such as in setup.py and --help output). <pkg_resources.EggInfoDistribution> supports retrieving this information via get_metadata(), but returns only a text blob. This has lead to projects re-implementing parsing logic in their codebases (i.e. mozilla/gecko-dev/.../utils.py#L20). Package data should instead be exposed as a dictionary or first-class object.
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.
Research direction
Start with pkg_resources.EggInfoDistribution.get_metadata(), then review how package metadata is used in setup.py and --help output, including the linked mozrunner/utils.py example. The issue is done when the structured package data it describes is exposed as a dictionary or first-class object rather than only a text blob.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100