[packaging] Implement SCM-based versioning via `setuptools-scm`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 408
- Avg merge
- 2d 57m
- Merged PRs (30d)
- 7
Description
Hi, have you considered using setuptools-scm plugin?
It'd automagically replace git ls-files logic in setup.py and it can also add a single source of truth for storing dist version.
With it, you'd use Git tags and wouldn't have to manually hardcode the version in two places https://github.com/libgit2/pygit2/blob/master/pygit2/_build.py#L40 / https://github.com/libgit2/pygit2/blob/master/.travis.sh#L5.
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 reading setup.py, pygit2/_build.py, and .travis.sh, then compare the current git ls-files and version handling with setuptools-scm's documented integration. Done means the packaging workflow uses Git-based versioning without duplicated hardcoded versions and continues to produce the expected distribution contents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100