Dev Stack Source

Answer : To install a specific package: conda install <pkg>=<version> eg: conda install matplotlib=1.4.3 There is no version 1.3.0 for rope . 1.3.0 refers to the package cached-property . The highest available version of rope is 0.9.4 . You can install different versions with conda install package=version . But in this case there is only one version of rope so you don't need that. The reason you see the cached-property in this listing is because it contains the string "rope" : "cached-p rope erty" py35_0 means that you need python version 3.5 for this specific version. If you only have python3.4 and the package is only for version 3.5 you cannot install it with conda. I am not quite sure on the defaults either. It should be an indication that this package is inside the default conda channel. If any of these characters, '>', '<', '|' or '*', are used, a single or double quotes must be...

Answer : Although you were offered a good solution by others I think it is helpful to point out what is really happening. As per the Anaconda 4.4 changelog, https://docs.anaconda.com/anaconda/reference/release-notes/#what-s-new-in-anaconda-4-4: On Windows, the PATH environment variable is no longer changed by default, as this can cause trouble with other software. The recommended approach is to instead use Anaconda Navigator or the Anaconda Command Prompt (located in the Start Menu under “Anaconda”) when you wish to use Anaconda software. (Note: recent Win 10 does not assume you have privileges to install or update. If the command fails, right-click on the Anaconda Command Prompt, choose "More", chose "Run as administrator") This is a change from previous installations. It is suggested to use Navigator or the Anaconda Prompt although you can always add it to your PATH as well. During the install the box to add Anaconda to the PATH is now unchecked but you can ...

Answer : The graphviz conda package is no Python package. It simply puts the graphviz files into your virtual env's Library/ directory. Look e.g. for dot.exe in the Library/bin/ directory. To install the `graphviz` **Python package**, you can use `pip`: `conda install pip` and `pip install graphviz`. Always prefer conda packages if they are available over pip packages. Search for the package you need (`conda search pkgxy`) and then install it (`conda install pkgxy`). If it is not available, you can always build your own conda packages or you can try anaconda.org for user-built packages. Update : There exists now a python-graphviz package at Anaconda.org which contains the Python interface for the graphviz tool. Simply install it with conda install python-graphviz . (Thanks to wedran and g-kaklam for posting this solution and to endolith for notifying me). On conda: First install conda install graphviz Then the python-library for graphviz python-graphviz ...

Answer : In Windows, you will have to set the path to the location where you installed Anaconda3 to. For me, I installed anaconda3 into C:\Anaconda3 . Therefore you need to add C:\Anaconda3 as well as C:\Anaconda3\Scripts\ to your path variable, e.g. set PATH=%PATH%;C:\Anaconda3;C:\Anaconda3\Scripts\ . You can do this via powershell (see above, https://msdn.microsoft.com/en-us/library/windows/desktop/bb776899(v=vs.85).aspx ), or hit the windows key → enter environment → choose from settings → edit environment variables for your account → select Path variable → Edit → New . To test it, open a new dos shell, and you should be able to use conda commands now. E.g., try conda --version . Things have been changed after conda 4.6 . Programs "Anaconda Prompt" and "Anaconda Powershell" expose the command conda for you automatically. Find them in your startup menu. If you don't wanna use the prompts above and try to make conda available in a normal cmd.exe a...

Answer : opencv is not compatible with python 3. I had to install opencv3 for python 3. The marked answer in how could we install opencv on anaconda? explains how to install opencv(3) for anaconda: Run the following command: conda install -c https://conda.binstar.org/menpo opencv I realized that opencv3 is also available now, run the following command: conda install -c https://conda.binstar.org/menpo opencv3 Edit on Aug 18, 2016: You may like to add the "menpo" channel permanently by: conda config --add channels menpo And then opencv can be installed by: conda install opencv (or opencv3) Edit on Aug 14, 2017: " clinicalgraphics " channel provides relatively newer vtk version for very recent python3 conda install -c clinicalgraphics vtk Edit on April 16, 2020 (based on @AMC's comment): OpenCV can be installed through conda-forge (details see here) conda install -c conda-forge opencv You can try conda install -c menpo opencv=3 Use this cod...

Answer : TL;DR: dependency conflicts: Updating one requires (by it's requirements) to downgrade another You are right: conda update --all is actually the way to go 1 . Conda always tries to upgrade the packages to the newest version in the series (say Python 2.x or 3.x). Dependency conflicts But it is possible that there are dependency conflicts (which prevent a further upgrade). Conda usually warns very explicitly if they occur. e.g. X requires Y <5.0, so Y will never be >= 5.0 That's why you 'cannot' upgrade them all. Resolving To add: maybe it could work but a newer version of X working with Y > 5.0 is not available in conda. It is possible to install with pip, since more packages are available in pip. But be aware that pip also installs packages if dependency conflicts exist and that it usually breaks your conda environment in the sense that you cannot reliably install with conda anymore. If you do that, do it as a last resort and af...

Answer : Name-based reference of Conda environments only works for environments located in one of the directories listed in the envs_dirs configuration option (see conda config --describe envs_dirs ). By default this corresponds to the envs/ subdirectory in the Conda installation. If you create an env outside of one of these directories, then you cannot use a name to reference it. Option 1: Clone Into Directory One option to use conda activate B3 , is to recreate your B3 env in the default directory. You can use the --clone flag to accomplish this. conda create --clone path/to/the/nameless_env -n named_env Option 2: Add Parent Directory Alternatively, you can add the parent directory of the environment in question to the envs_dirs configuration option. conda config --append envs_dirs /path/to/the/parent_dir Option 3: Symbolic Link Another possibility is to create a symbolic link in one to the envs_dirs folders to the environment folder. It seems to work, but it is not a commo...

Answer : Per the original docs: Choose Anaconda if you: Are new to conda or Python Like the convenience of having Python and over 1500 scientific packages automatically installed at once Have the time and disk space (a few minutes and 3 GB), and/or Don’t want to install each of the packages you want to use individually. Choose Miniconda if you: Do not mind installing each of the packages you want to use individually. Do not have time or disk space to install over 1500 packages at once, and/or Just want fast access to Python and the conda commands, and wish to sort out the other programs later. I use Miniconda myself. Anaconda is bloated. Many of the packages are never used and could still be easily installed if and when needed. Note that Conda is the package manager (e.g. conda list displays all installed packages in the environment), whereas Anaconda and Miniconda are distributions. A software distribution is a collection of packages, pre-built and pre-configured, ...

Answer : If you're using zsh and it has not been set up to read .bashrc, you need to add the Miniconda directory to the zsh shell PATH environment variable. Add this to your .zshrc : export PATH="/home/username/miniconda/bin:$PATH" Make sure to replace /home/username/miniconda with your actual path . Save, exit the terminal and then reopen the terminal. conda command should work. If you have the PATH in your .bashrc file and are still getting conda: command not found Your terminal might not be looking for the bash file. Type bash in the terminal to insure you are in bash and then try: conda --version For those experiencing issues after upgrading to MacOS Catalina. Short version: # 1a) Use tool: conda-prefix-replacement - # Restores: Desktop -> Relocated Items -> Security -> anaconda3 curl -L https://repo.anaconda.com/pkgs/misc/cpr-exec/cpr-0.1.1-osx-64.exe -o cpr && chmod +x cpr ./cpr rehome ~/anaconda3 # or if fails #./cpr rehome ~/anaconda3 --old...

Answer : If you want to set specific version, use it like this: WARNING: This command will overwrite the default python version system-wise conda install python=3.6 To create environment with a specific version, you can do: conda create -n $PYTHON36_ENV_NAME python=3.6 anaconda # set custom env name The anaconda at the end allows the env to use all anaconda packages For more information refere to Anaconda documentation You can make environments with other versions of Python using this command: conda create --name py33 python=3.3 source activate py33