Hi everyone,
* Ben Westover <
[email protected]> [2022-06-06 22:42]:
As far as I understand it, this file is used by the author of the
program, not end users. I don't understand it well, though, because I >haven't put much time into researching what versioneer even does.
Versioneer is meant to simplify version tracking for the developer;
it supports a number of authoritative sources such as "git
describe" to determine the current version number. There are two
modes of operation:
- in developer mode, versioneer detects the version number
dynamically. This is what you'll see if you use the (Git)
repository sources.
- in install mode, the release version number is statically
embedded. This is what you'll see if
you download from PyPI.
Internally, these modes are realized by two different _version.py
files; the developer version is usually added to version control,
and the setuptools "build" and "sdist" steps are
intercepted to insert the static _version.py as needed.
In my experience, it Just Works with pybuild, so I wouldn't bother
with any special treatment; the versioneer.py source is public
domain, so you're not going to run into any licensing issues.
Cheers
Timo
--
⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │
⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
-----BEGIN PGP SIGNATURE-----
iQGzBAABCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmKfXNYACgkQ+C8H+466 LVngSQwAjR7vb7EZGMZBS4/xvVuPZWIiFjVJTvRnmSto3Go6gTTQ7ulNgg9TtTlB rzHFKGbThJMC2c5dY61eSMA8BOoM9Z5PJVGTcAA/DxlgQEZz9fUw91E8xU4mEw1E eTntUUNmfj8OrNMGxJsHUe1Ovhs8q8wVx4uKyd/Ky/xFNDAYRtVjWWmbcxgm4qBs TxSokeibHe37FkdktGv75JgaBKRXsy56Xe9ZIAOJ6fQGgeXTQ55gkD3kEJvIJJie 1pGcJWjG+TawRUfONMDyBZFIASKbiGeEUFt6KhpEoB+a3OHoIR9iTIA9X/P+zPeb OLAz8uyJ1fZPh1z9cgKinyZPRAOUkqtFmyufC5j19oj