Well I did not use travis because I thought it was a little cumbersome to
have to push every little change I made to my Github repo, plus a travis
build takes ~15 min. I was looking for a way to keep the binaries for both
versions with the same source directory (I don't do edit cython files for
> I don't see an easy way to maintain the changes in two different
directories.
If both directories are Git repositories linked to a common remote, you
could commit the changes on a branch and then sync them that way.
Jake VanderPlas
Senior Data Science Fellow
Director of Research in Physical
Hi Antoine,
For this type of thing I use conda environments:
http://conda.pydata.org/docs/using/envs.html
The other thing to keep in mind is that if you're installing from the same
source directory, you'll need to do a clean install each time; i.e. type
``python setup.py clean`` before typing
Hello Jake,
Thanks for your answer. I am already using conda, and having to clean and
rebuild everything everytime I want to switch versions is what I want to
avoid, since it's a bit long to accomplish. Using two different source
folders seems a bit silly since I would like to test changes I just
Hi everyone,
I am using conda in order to be able to test scikit-learn for different
python versions. The problem I have is whenever I build scikit-learn for
one version of python it messes up the installation of scikit learn for the
other version, and when I try to run tests I get the "It seems
On 01/25/2016 02:56 PM, WENDLINGER Antoine wrote:
> Hello Jake,
>
> Thanks for your answer. I am already using conda, and having to clean
> and rebuild everything everytime I want to switch versions is what I
> want to avoid, since it's a bit long to accomplish. Using two
> different source
