-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
Versioneer reported version of dev build is incorrect #15156
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
@jcrist When installed with pip from github directly, does it give you |
(pandas) jcrist ~ $ pip install git+https://github.com/pandas-dev/pandas.git
Collecting git+https://github.com/pandas-dev/pandas.git
Cloning https://github.com/pandas-dev/pandas.git to /var/folders/vl/xj_l5ml95sbfm7x480g60x440000gp/T/pip-jRkfFH-build
Requirement already satisfied (use --upgrade to upgrade): python-dateutil in ./anaconda/envs/pandas/lib/python2.7/site-packages/python_dateutil-2.5.3-py2.7.egg (from pandas==0.19.0+343.g8e13da2)
Requirement already satisfied (use --upgrade to upgrade): pytz>=2011k in ./anaconda/envs/pandas/lib/python2.7/site-packages/pytz-2016.6.1-py2.7.egg (from pandas==0.19.0+343.g8e13da2)
Requirement already satisfied (use --upgrade to upgrade): numpy>=1.7.0 in ./anaconda/envs/pandas/lib/python2.7/site-packages (from pandas==0.19.0+343.g8e13da2)
Requirement already satisfied (use --upgrade to upgrade): six>=1.5 in ./anaconda/envs/pandas/lib/python2.7/site-packages/six-1.10.0-py2.7.egg (from python-dateutil->pandas==0.19.0+343.g8e13da2)
Installing collected packages: pandas
Running setup.py install for pandas ... done
Successfully installed pandas-0.19.0+343.g8e13da2
You are using pip version 8.1.2, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
(pandas) jcrist ~ $ python -c "import pandas;print(pandas.__version__)"
0.19.0+343.g8e13da2 Versioneer just grabs the version from (pandas) jcrist pandas $ git describe --tags --dirty --always --long
v0.19.0-343-g8e13da2 |
we don't have a concept of minor release detection anymore, as the master branch (ATM) is all encompasing, from >= 0.19.0 till now. So detection of something that started existing only in 0.19.2 is theoretically impossible via the tags, though obviously via duck typing it is. So solutions are:
|
Another option would be to tag master with eg In that case a check like " >= 0.19.2" would work for both master and 0.19.2 (but of course is only correct if your master is up to date) |
closing |
Sometimes it's nice to install projects from master to get recent fixes (e.g.
pip install git+https://github.com/pandas-dev/pandas.git
). However, since pandas switched to using dev branches for0.19.1+
, versioneer incorrectly reports the version of the dev build as0.19.0
. This breaks checks for version, e.g. the following would report false for a build off master, when semantically master is after the 0.19.2 release:I'm not sure if there is an easy/good fix for this, just opening this to discuss.
The text was updated successfully, but these errors were encountered: