setuptools-scm-patch

A tiny patch for setuptools_scm to customize version formatting.

Transforms versions like: foo-0.3.1.dev21+g6c51818 into: foo-0.3.21+g6c51818

Installation

Add setuptools-scm-patch to your pyproject.toml:

[build-system]
requires = [
  "setuptools>=64",
  "setuptools_scm>=8",
  "setuptools-scm-patch", # <<< Add this
]
build-backend = "setuptools.build_meta"

Configuration

Enable the custom version scheme in pyproject.toml:

[project]
# ...
dynamic = ["version"]

[tool.setuptools_scm]
version_scheme = "setuptools_scm_patch:simple_version_scheme"

License

MIT

Metadata

Release files for setuptools-scm-patch 1.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for setuptools-scm-patch 1.0.1
File	Interpreter	ABI	Platform	Reset
setuptools_scm_patch-1.0.1-py3-none-any.whl 1.7 kB Apr 15, 2025 Without provenance	Python 3	none	any	Details

Release files / setuptools_scm_patch-1.0.1-py3-none-any.whl

Download URL	setuptools_scm_patch-1.0.1-py3-none-any.whl
Size	1.7 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`f49854bddcaac32d4aa8c1230eafc303070b4e8f1b7ca042cefa3c1a0847b823`
BLAKE2b-256 checksum How to use checksums	`dbe1481833a439097125b97b37425e06c5d4a1bf7c340db25d1ccc645e6978f4`
Upload date	Apr 15, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/6.1.0 CPython/3.12.2`

Security for setuptools-scm-patch 1.0.1

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.