-
Notifications
You must be signed in to change notification settings - Fork 93
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
New release needed #69
Comments
I think it's pretty standard practice to have |
Thanks for the inputs. I agree with both of you that the stable and in-development versions shouldn't have the same version number. That was a mistake on my side, I'll fix it next release. I like the idea of explicitly marking that it is a development version with the
|
Are there any plans to release master? Pypi version is over 3 years old now, and this issue is over 1 year old. Or is there an alternative to pypi I should be using (e.g. conda) or some fork I should be following? |
There are plans, but as you can imagine, they are slipping... We are still committed to develop and maintain the package. Our idea would be to first merge some long-standing PRs. Nowadays it's pretty easy to install from github: |
I did not know that! Maybe that should be added to the README installation section. Unfortunately, when I tried it with --upgrade it just said requirement already satisfied. I think it is because main branch references 0.5.1 and not 0.5.2-alpha/snapshot or something, which is what the original issue is about. So, your solution would be ideal if it wasn't for that :( |
And there's pip magic for this issue too: |
You forgot to drop the mike!Awesome.Next you will be telling me that I can specify all this in a requirements.txt...
|
In a
|
This is certainly going to revolutionise my usage of pip across the board. |
The release we get with pypi is 0.5.1 and the version on the master branch is also tagged 0.5.1 even if it has many new features. It confuses people, especially when looking at the doc. People mix the 'stable' and 'latest' tag in the doc. I would suggest to make a new release.
I guess it would solve some of the issues opened. I also had students confused during a course on networks and data science where they use it for their project.
Happy new year! :)
The text was updated successfully, but these errors were encountered: