Use version control tags to discover version numbers
Elevator pitch: you can write a setup.py with no version information
specified, and vcversioner will find a recent, properly-formatted
VCS tag and extract a version from it.
It’s much more convenient to be able to use your version control
system’s tagging mechanism to derive a version number than to have
to duplicate that information all over the place. I eventually ended
up copy-pasting the same code into a couple different setup.py files
just to avoid duplicating version information. But, copy-pasting is
dumb and unit testing setup.py files is hard. This code got factored
out into vcversioner.
- Sources inherited from project SUSE:SLE-15:GA
-
Checkout Package
osc checkout SUSE:SLE-15-SP1:Update/python-vcversioner && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
COPYING | 0000000753 753 Bytes | |
python-vcversioner.changes | 0000000685 685 Bytes | |
python-vcversioner.spec | 0000002122 2.07 KB | |
vcversioner-2.16.0.0.tar.gz | 0000009024 8.81 KB |
Revision 1 (latest revision is 3)
Samu Voutilainen (Smar)
committed
(revision 1)
osc copypac from project:SUSE:SLE-15:GA package:python-vcversioner revision:1, using expand, using client side copy
Comments 0