setuptools_scm
setuptools_scm copied to clipboard
pypa
the blessed package to manage your versions by scm tags
Hey team 👋 It was a not so happy Sunday for us at our company as we started our week with dreaded message: `ModuleNotFoundError: No module named 'setuptools.command.build'` Working with...
### Issue 1 No pre-release in version tuple. Contents of the version file generated from tag v1.0.0a1 (HEAD is at tag): ``` 8228a06 (HEAD, tag: v1.0.0a1) added setuptools-scm 624de26 initial...
When a `pyproject.toml` file is used with "build" as the build frontend and "setuptools" as the build backend, and when dynamic versioning is used with "setuptools-scm", then the specifications in...
The `no-local-version` scheme is nice if you want to upload to TestPyPI since it does not accept nodes in the version. However, this makes every version in between tags the...
Instead of asking git what the relative path of the current directory is from the root of the repository and then reverse-engineering the root, simply call git rev-parse --show-toplevel. This...
Reproduction 1. `git clone https://github.com/Quansight/ragna` 2. `cd ragna` 3. `git checkout dca421b40ebd6876b2d71b624ab9689bd113139a` 4. `conda env create -f environment-dev.yml -n stscm-debug` 5. `conda activate stscm-debug` 6. `echo 'random change' >> README.md`...
> thanks for the update - hat one is a neat workaround - we should probably put it to the docs _Originally posted by @RonnyPfannschmidt in [#962](https://github.com/pypa/setuptools-scm/issues/962#issuecomment-2595226198)_
Using the `release-branch-semver` scheme, a commit five nodes off e.g. `1.0.0` will get `1.1.0dev5`, but a commit four nodes off `1.0.1` will get `1.1.0dev4`, despite it being more commits from...
If two tags are assigned to the same git-commit, `setuptools-scm` seems to get confused (especially if the secondary tag contains digits or ends with digits). ## How to repeat *...
