-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Report version in index page. #427
Conversation
Perhaps adopting a best practice recommend here : https://packaging.python.org/guides/single-sourcing-package-version/ |
Codecov Report
@@ Coverage Diff @@
## master #427 +/- ##
=======================================
Coverage 79.88% 79.88%
=======================================
Files 33 33
Lines 4101 4102 +1
=======================================
+ Hits 3276 3277 +1
Misses 825 825
|
Added legacy setuptools support. E.g. scm-versionise your git source control directory by running:
Your version will then display correctly and the created file will be ignored by git. You will need to re-run this every time you commit or pull though. |
We use #7 from that list. |
I did have a try myself at this yesterday, what I found is when I run commandline However, when it renders on the |
no luck yet
|
Yeah there seems to be some unexpected interaction with the docker build. Looking into it. |
Hmmm... Appears to be a known issue in pip: pypa/pip#7549 I'm working on a workaround. Longer term fix is pushing releases to PyPI |
Lol, I get it. It's because git isn't installed in the container so when you run "pip install ." in the docker build it can't determine the version number from git. I'll fix it tomorrow. |
For #423
Will work more smoothly when we publish tags to PyPI.
For now, you must run:
This derives the version number from git.
Should work automagically in Docker.