-
Notifications
You must be signed in to change notification settings - Fork 255
Development versions should have a distinct version number #687
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
Comments
I'll probably look into this, but it seems like this would also involve officially dropping support for Python 3.7. (Python 3.7 has reached EOL three days ago, so in theory we could drop support for it right now and it wouldn't go against our own policies). The reason is that igraph's version number currently comes from |
I added the milestone by accident, this doesn't need to be done now. Let's do it only when we're ready. It's not worth dropping support for old versions just because of this one issue, not even if that Python version is out of support. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Can we please have distinct version numbers for development versions? For example, the current
main
branch could show0.10.4.bignumber
wherebignumber
is something derived from the present git commit. Right now it simply shows 0.10.4.When looking at #685, at one point I was under the impression that I was running 0.10.4 while in reality I was using the dev version.
The text was updated successfully, but these errors were encountered: