Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #14151
| From | Timo Röhling <roehling@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Versioneer [was Re: a review of your bumblebee-status package] |
| Date | 2022-06-07 16:30 +0200 |
| Message-ID | <EvInv-3dvH-5@gated-at.bofh.it> (permalink) |
| References | <EvuXf-34C0-3@gated-at.bofh.it> <EvuXf-34C0-1@gated-at.bofh.it> <Evw2Z-35cy-1@gated-at.bofh.it> <Evx8J-35Wo-1@gated-at.bofh.it> <Evxs5-3638-1@gated-at.bofh.it> |
| Organization | The Debian Project |
[Multipart message — attachments visible in raw view] - view raw
Hi everyone, * Ben Westover <kwestover.kw@gmail.com> [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 │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: a review of your bumblebee-status package Ben Westover <kwestover.kw@gmail.com> - 2022-06-07 02:10 +0200
Re: a review of your bumblebee-status package Ben Westover <kwestover.kw@gmail.com> - 2022-06-07 03:20 +0200
Re: a review of your bumblebee-status package Antoine Beaupré <anarcat@debian.org> - 2022-06-07 04:30 +0200
Re: a review of your bumblebee-status package Ben Westover <kwestover.kw@gmail.com> - 2022-06-07 04:50 +0200
Re: a review of your bumblebee-status package Andrey Rahmatullin <wrar@debian.org> - 2022-06-07 08:20 +0200
Re: a review of your bumblebee-status package Julian Gilbey <julian@d-and-j.net> - 2022-06-07 08:20 +0200
Re: a review of your bumblebee-status package Antoine Beaupré <anarcat@debian.org> - 2022-06-07 15:50 +0200
Re: a review of your bumblebee-status package Julian Gilbey <julian@d-and-j.net> - 2022-06-07 16:50 +0200
Re: a review of your bumblebee-status package Julian Gilbey <julian@d-and-j.net> - 2022-06-07 17:00 +0200
Re: a review of your bumblebee-status package Ben Westover <kwestover.kw@gmail.com> - 2022-06-08 00:50 +0200
Re: a review of your bumblebee-status package Antoine Beaupré <anarcat@debian.org> - 2022-06-08 15:30 +0200
Re: a review of your bumblebee-status package Antoine Beaupré <anarcat@debian.org> - 2022-06-07 17:00 +0200
Re: a review of your bumblebee-status package Antoine Beaupré <anarcat@debian.org> - 2022-06-07 15:50 +0200
Re: a review of your bumblebee-status package Julian Gilbey <julian@d-and-j.net> - 2022-06-07 17:00 +0200
Re: a review of your bumblebee-status package Julian Gilbey <julian@d-and-j.net> - 2022-06-07 17:10 +0200
Versioneer [was Re: a review of your bumblebee-status package] Timo Röhling <roehling@debian.org> - 2022-06-07 16:30 +0200
Re: Versioneer [was Re: a review of your bumblebee-status package] Paul Wise <pabs@debian.org> - 2022-06-08 03:30 +0200
csiph-web