---
id: vcver
version: "0.2.12"
license: unclear
license_treatment: permissive
maintenance: abandoned
---

# vcver — provide package versions with version control data.

License: permissive · Maintenance: abandoned · Downloads: 498.9K/mo

## What it is and what it does

vcver is a setup tool that automatically generates version strings for Python packages by reading version control metadata. It produces two types of versions: development versions (e.g., 1.1.dev10+master.abc123) that include commit count, branch, and change ID for debugging, and release versions (e.g., 1.1) taken directly from git tags. The tool is designed to work with setuptools during the build process and writes a VERSION file that can be included in source distributions.

The package solves the problem of keeping package versions in sync with version control without manual version bumping in setup.py. It distinguishes between release branches (where versions come from tags) and development branches (where versions are zeroed out to prevent accidental installation of development builds). All generated versions comply with PEP440.

Use it for:

- Automatically version Python packages from git tags without manually updating setup.py for each release
- Generate development version strings that encode branch and commit information for debugging build artifacts
- Prevent accidental installation of development branch versions by zeroing out non-release branch versions
- Include version metadata in source distributions via a generated VERSION file for offline builds

## Worth the install?

AI-flagged interpretation of the facts above — verify before relying.

vcver generates version strings for Python packages by extracting version information from version control systems, producing development versions with commit metadata and release versions from tags.

No. The package is abandoned (last release 2021-08-10, no commits since) and targets legacy setuptools workflows. Only install if you have an existing project already using vcver and cannot migrate to actively maintained alternatives.

## Install

pip install vcver
uv add vcver
poetry add vcver

## Installing vcver

Before you install: Low install friction with a single lightweight dependency (packaging). However, the package is abandoned—last release was 2021-08-10 with no commits since then. Use only if your project's versioning approach aligns with its design and you can maintain it yourself if needed.

License in practice: Licensed under MIT (permissive), so there are no restrictions on commercial or proprietary use. You may use, modify, and distribute the package freely as long as you retain the license notice.

Quickstart:

# In setup.py
import vcver
setup(
    name='mypackage',
    setup_requires=['vcver'],
    vcver={'is_release': False, 'path': os.path.dirname(__file__)}
)
# vcver generates a VERSION file with the computed version string

Requires a version control repository (git, hg, etc.) or a VERSION file in the package directory; vcver will not work in a bare source tree without SCM metadata.

Verify before relying:

- Whether vcver works correctly with Python versions released after 2021-08-10, given the last release date and abandoned status
- Current compatibility with modern setuptools build workflows versus the legacy setup.py-only approach documented

## Package facts

- License: not declared (permissive)
- Python support: unspecified
- Install friction: low
- Maintenance: abandoned
- Downloads: 498.9K/month (top 15,000 on PyPI)
- Known vulnerabilities: none known

## Tags

version control based versioning, automatic version from git tags, vcver version generation, setuptools version from scm, development version strings, pep440 version from vcs, version-control-integration, setuptools-plugin

[View on SkillFed](https://skillfed.io/packages/vcver) · [View on PyPI](https://pypi.org/project/vcver/)