Tag prefix broken on Windows with versioneer 0.21
See original GitHub issuehttps://github.com/python-versioneer/python-versioneer/pull/262 contains a fix for handling * on windows unfortunately this breaks detecting the correct version for me.
In our repository https://github.com/qcodes/qcodes all tags are prefixed with v
and we have tag_prefix = v
this used to work fine however with the latest release of versioneer we get versions reported as unknown + x
Looking at the generated git describe
command we see
git describe --tags --always --long --dirty --match v*
v0.29.0-288-g9f93a1286
git describe --tags --always --long --dirty --match v\*
9f93a1286
git describe --tags --always --long --dirty --match v\\*
9f93a1286
so it would seem like the escape of * does not always work correctly. removing the escaped prefix for windows restores normal functionality for us
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:15 (5 by maintainers)
Top Results From Across the Web
How to update versioneer version prefix? - Stack Overflow
It seems the tag-prefix can be overwritten by setting a tag with git. git tag 0.0.31. Followed by pip install -e .
Read more >versioneer — NiftyNet 0.6.0 documentation - Read the Docs
Some projects use tag names that include more than just the version ... which case the tool needs to strip the tag prefix...
Read more >Changelog - Dask documentation
Fix map_overlap in order to accept pandas arguments (GH#9571) Fabien Aulaire ... Update versioneer: change from using SafeConfigParser to ConfigParser ...
Read more >Compare Packages Between Distributions - DistroWatch.com
atf 0.21 atftp 0.8.0 athcool 0.3.12 atheme-services 7.2.12 atk 2.46.0 atkmm 2.36.2 ... broken-age 2.4.800398 broot 1.16.2 ... cucumber-tag-expressions 4.1.0
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@hwjohn I’ll take that into account and also see if the tag prefix works consistently on all platforms if it is provided.
@mathijsvdv , I would be grateful if you provided a fix.
I think a better solution than what is currently implemented in #274 is to just omit the
--match
option entirely from thegit
command if there is no tag prefix. This will avoid any issues with trying to predict the correct escape sequence for a given platform.