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

Travis Problem #487

Closed
blink1073 opened this Issue Nov 30, 2014 · 11 comments

Comments

Projects
None yet
3 participants
@blink1073

blink1073 commented Nov 30, 2014

Hi all, I tried to copy what you're doing with your .travis.yml file for skimage. However, it looks like the virtualenv is not respecting the TRAVIS_PYTHON_VERSION. It looks like this across versions:

$ virtualenv venv
$ source venv/bin/activate
$ python --version
Python 2.7.3
@blink1073

This comment has been minimized.

blink1073 commented Nov 30, 2014

cc/ @stefanv

@blink1073

This comment has been minimized.

blink1073 commented Nov 30, 2014

This works:

$ pip install virtualenv
$ virtualenv venv
$ source venv/bin/activate
$ python --version
Python 2.6.9
@blink1073

This comment has been minimized.

blink1073 commented Nov 30, 2014

Travis makes me feel insane sometimes, how about y'all?

@matthew-brett

This comment has been minimized.

Member

matthew-brett commented Nov 30, 2014

No wonder all the tests pass !

I think virtualenv --python=python venv will also do it though.

@matthew-brett

This comment has been minimized.

Member

matthew-brett commented Nov 30, 2014

Travis - insane - why yes.

But in this case, the behavior on my machine looks to be the same. Not sure why your pip install worked...

@blink1073

This comment has been minimized.

blink1073 commented Nov 30, 2014

I was pasting from the Travis logs.

@blink1073

This comment has been minimized.

blink1073 commented Nov 30, 2014

I accidentally called an acquaintance "Travis" after having battled with Travis for a whole day, now I still call him that as a joke.

@blink1073

This comment has been minimized.

blink1073 commented Nov 30, 2014

Here's my final working incantation:

$ virtualenv -p python --system-site-packages ~/venv
$ source ~/venv/bin/activate
@matthew-brett

This comment has been minimized.

Member

matthew-brett commented Nov 30, 2014

I guess you friend now called Travis is someone you can't really do without, but is unreliable and has some strange habits :)

I personally prefer to keep the virtualenvs clean so I know what I'm installing, but I believe using the system site packages does get you a numpy without a pip install.

Dipy builds seem to be working correctly with just the -p python bit : https://travis-ci.org/matthew-brett/dipy/builds/42520626

Thanks very much for pointing that out - very easy to miss.

matthew-brett added a commit to matthew-brett/dipy that referenced this issue Nov 30, 2014

BF: fix travis version setting
Luckily Steven Silvester noticed that selecting Python versions for the
virtualenvs was not working : nipy#487
@blink1073

This comment has been minimized.

blink1073 commented Dec 1, 2014

I'm tempted to leave this open as a place to vent Travis frustrations, but life goes on, cheers!

@blink1073 blink1073 closed this Dec 1, 2014

@stefanv

This comment has been minimized.

Contributor

stefanv commented Dec 1, 2014

Thanks a million guys--so happy not to have had to tackle this one myself ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment