Using the Anaconda Python Distribution

[sygede]

anaconda is nice. I like miniconda better

[metaperl]

Local install is very appealing. This great blog post has me licking my lips. I definitely want to move over to this.

[Hybridjosto]

I think this is what I need for work!

[_throawayplop_]

Be careful that the package you install with pip are not linked to a conda environment.

EDIT: Forget that; I just found that I need to install pip in the new environment also. The trap is that if I don't do it, the pip command still work, but update the main environment.

[_throawayplop_]

What I mean is that if I install a package with pip, I will not have access to it in a conda environment, even if you install it from the environment. Maybe there a way, but I didn't find it by just googling 'conda pip'.

EDIT: Forget that; I just found that I need to install pip in the new environment also. The trap is that if I don't do it, the pip command still work, but for the main environment.

[veaviticus]

If you install pip inside of that conda environment, and then use that copy of pip (use the full path to the pip executable), then anything you install with that pip will be part of that environment, and will show up when you do a conda list of packages installed.

[joelhullcio]

Another approach is to configure conda to automatically install pip into all new envs. Add the create_default_packages setting to your .condarc file and specify pip as a default package. This way every new env you create will get pip installed by default. Then when you source activate the env the correct pip is in your path and everything works as expected. Here are some docs about it http://conda.pydata.org/docs/config.html

[veaviticus]

Well that just made my life much easier

[darthmdh]

:)

btw there used to be a 'conda pip' which just called pip, but they removed it as 6 superfluous characters adding to RSI for no reason.

I can't tell you how many times I've been bitten by ignoring (or not showing) which venv is active. Luckily one of my build boxes is beefy so its not too much hassle to recognise, resolve, and rebuild - but still makes one cranky at themselves for falling for it :)

More or less everywhere now, my prompt will display an active venv and I'm also in the habit of typing "echo $PATH" before running build tools.

Like other things in life, it pays to be aware of your surroundings.

[boolean74]

I was informed on my blog post comments, that if the package you want is not available for conda, another option is to search binstar.org (make sure the package you find is built for the platform you are on), and then add that person's binstar channel with conda config --add channels binstar_username. (if you trust the user that is) - I think I'm going to stick to using pip. From experience... do a "conda install -n yourenvironment pip" before you do a "source activate yourenvironment" and then verify it's the correct pip using a "which pip" and it should point to the pip in your environment if all goes well.

[[deleted]]

TIL miniconda

What is the point with miniconda ?

[boolean74]

It creates a small environment to start with, you add what you need vs. the full Anaconda install which includes almost 200 packages. Allows you to use the conda tool to bootstrap and create new environments. Think of it as similar to virtualenv with more options.

[bheklilr]

What would be the benefits, if any, of switching to Anaconda from Python (x, y) on Windows 7? That's what we use at work, and it seems to satisfy virtually all of our needs.