-
Notifications
You must be signed in to change notification settings - Fork 31
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
Awkward Versioning on PyPi #1
Comments
Thanks for reporting this. I would like to leave the commiter date into the version string. Now i have change the way that this date added to the version string, with: c72661d I have made a simple filter for this, more info here: https://github.com/jedie/python-code-snippets/tree/master/CodeSnippets/git/ I hope that the reported issues is fixed with this. Please reopen and report if problems still exists... |
Thanks for the quick turn around! |
btw. IMHO it's a better idea to add a range in your requirements file! like:
I do it in this way, see: https://github.com/jedie/PyLucid/blob/master/requirements/normal_installation.txt |
I'm going to disagree with you there. I think it's a better idea to pin your requirements to the exact version that you want so that no developers or environments are running different versions even if they are just "bug fix" differences. Packages are not consistent in how they version projects. Some make much larger changes when going from In any case I came across this error because an coworker did
and as noted doing |
You where right, that version scheme are not consistent :( But i do it like this: |
After playing with git filter and creating a commit hook i decided to remove the date form version string completely with v0.24.4 |
The current version on django-tools on PyPi is
0.24.02.0710
. That alone is not that odd. However once installed the version is shown as0.24.02
. This creates problem with trying to pin the version with a requirements file demonstrated below:Now installing attempting to install this exact version errors:
And trying to install the version including the date stamp works (
pip install django-tools==0.24.2.0710
) but fails if it is in a requirements file (That this works on the command line but not in a requirements file is noted in a pip bug: pypa/pip#145):Removing the date stamp from the version number is probably the easiest solution but might not be desirable to you. In any case the version number should be constantly reported (always with the date or always without) to prevent this conflict error.
The text was updated successfully, but these errors were encountered: