setuptools_scm
setuptools_scm copied to clipboard
the blessed package to manage your versions by scm tags
Trying to use `setuptools_scm==7.1.0` on a brand new repository with no tags fails if `tag_regex` has been specified that does not match the default fallback version `0.0`, like the example...
- [ ] in the docs - [ ] in the sourcecode for overrides _Originally posted by @RonnyPfannschmidt in https://github.com/pypa/setuptools_scm/pull/981#discussion_r1413192120_
Hi, I'm building a package using `pyproject.toml` conf for setuptools_scm and I'm trying to customize the `local_scheme` part of the returned version to get rid of the date and keep...
Assuming the current comment has multiple tags, setuptools only picks the first one, when it would be better to pick that last one instead. Multiple tags on same commit are...
We use the following to automatically write a version file upon `pip install -e .` which then gets shipped within the container. ``` [tool.setuptools_scm] write_to = "path/to/somewhere/_scm_version.py" ``` During Python...
I use the `write_to` option in my `pyproject.toml` config file to write to a Python `__version__.py` file. It creates a file that looks like this: ```python # coding: utf-8 #...
Currently there are references to the required version being: - `>=60` - [README.md](https://github.com/pypa/setuptools_scm/blob/ceca2352f09ed22f825f45a392cca5aff83c6aff/README.md?plain=1#L29) - `>=61` - [runtime warning](https://github.com/pypa/setuptools_scm/blob/ceca2352f09ed22f825f45a392cca5aff83c6aff/src/setuptools_scm/_integration/setuptools.py#L37) - [your own pyproject.toml buld requirements](https://github.com/pypa/setuptools_scm/blob/ceca2352f09ed22f825f45a392cca5aff83c6aff/pyproject.toml#L9) - [your test workflow](https://github.com/pypa/setuptools_scm/blob/ceca2352f09ed22f825f45a392cca5aff83c6aff/.github/workflows/python-tests.yml#L82) - `>=62`...
IIUC, setuptools_scm does two things: 1) auto-generates a version from the SCM 2) generates a file list for the sdist from the SCM But as far as I can tell,...
# Background On github actions when running in a container, by default (at least in my container) the build directory isn't considered 'safe' by git because it has 'dubious ownership'....