Add basic configuration for `MANIFEST.in`?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 7
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 5
Description
We are configuring check-manifest to run, but we are not providing any default values for MANIFEST.in configuration file.
Should we? 🤔
Inside my buildout.coredev/src folder I have 204 repositories and only 2 of them do not have a MANIFEST.in (probably buildout repositories? 🤷🏾 ).
Seems that zopefoundation/meta is managing that, as doing cat */MANIFEST.in | sort | uniq -c | sort -g shows:
11 # https://github.com/zopefoundation/meta/tree/master/config/c-code
22 # https://github.com/zopefoundation/meta/tree/master/config/zope-product
49 # https://github.com/zopefoundation/meta/tree/master/config/pure-python
Contributor guide
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 by reviewing the check-manifest setup and the zopefoundation/meta templates referenced in config/c-code, config/zope-product, and config/pure-python. Compare those patterns with the repositories that lack MANIFEST.in, then determine whether a default should be standardized and which template or configuration would own it. Done means the policy is decided and the relevant meta configuration is updated if approved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100