Fix versionning from source archive
See original GitHub issueThe versionning is wrong when a wheel is built from the source archive on PyPI.
The version should be 0.9.10
but it is 0+untagged.325.g2863b82.dirty
.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
7. Releasing and versioning - Python Packages
If you change the package's source code, their code could potentially break (imagine you change a module name, or remove a function argument...
Read more >Version control concepts and best practices
Version control gives access to historical versions of your project. This is insurance against computer crashes or data lossage. If you make a...
Read more >Putting Versions in the Code is a Deadly Sin Against Liquid ...
Simply put, having versions in one's code is bad. It requires the existence of a file within a code base that identifies a...
Read more >Semantic Versioning 2.0.0 | Semantic Versioning
The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release....
Read more >Schedule re-archive - versioning · Discussion #687 - GitHub
I'm using that command to each website i want a new archive version every monday at 2 AM : archivebox schedule --every="0 2...
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 Free
Top 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
Hi @ml31415 Thank you very much for fixing this and publishing
0.9.11
. Everything’s working well now! 🥳Thanks for pointing this out! The pypi package should be fixed with the latest bugfix release. About installing from the github master zip: Versioneer creates a new _version.py file whenever a distribution package is created. This process would have to run, when the github release master.zip is created. I might add this when setting up CI with the github workflows at some point.
For now I hope the pypi fix is sufficient for everyone involved. If not, please open a separate bug.