To create python 3.11 conda environment use the following command conda create -n py311 python=3.11 py311 – environment name Update 3 To create python 3.10 conda environment use the following command conda create -n py310 python=3.10 py310 – environment name Update 2 You can now directly create python 3.9 environment using the following command conda … Read more
You can just use pip for installing packages, even when you are using anaconda: pip install -U scikit-learn scipy matplotlib This should work for installing the package. And for Python 3.x just use pip3: pip3 install -U scikit-learn scipy matplotlib
I can’t find anything in the conda specs which allows you to export an environment file without the prefix: … line. However, like Alex pointed out in the comments, conda doesn’t seem to care about the prefix line when creating an environment from the file. With that in mind, if you want the other user … Read more
Names and Prefixes For a Conda environment to have a name it must be installed in one of the envs_dirs directories (see conda config –show envs_dirs). Creating an environment outside of one of those forfeits its “name-ability”. Instead, one must use the path (called its prefix) to activate it, e.g., conda activate /anaconda3/envs/my_env Other commands … Read more
I am not sure what causes the problem in your case, but code below works for me without any issues (OS X, the same version of Conda as yours). Creation of the environment conda create -n test_env python=3.6.3 anaconda Some explanation of the documentation of conda create is not clear: -n test_env sets name of the … Read more
Configure Environment and Package Default Locations I’d guess that, despite your efforts to put your environments on the large partition, there is still a default user-level package cache and that is filling up the home partition. At minimum, set up a new package cache and a default environments directory on the large partition: # create … Read more
Followed this tutorial and it worked. Example Dockerfile: FROM continuumio/miniconda WORKDIR /usr/src/app COPY ./ ./ RUN conda env create -f environment.yml # Make RUN commands use the new environment: SHELL [“conda”, “run”, “-n”, “myenv”, “/bin/bash”, “-c”] EXPOSE 5003 # The code to run when container is started: ENTRYPOINT [“conda”, “run”, “-n”, “myenv”, “python3”, “src/server.py”] Update: … Read more
You might want to try this: For Anaconda 2: export PATH=~/anaconda2/bin:$PATH For Anaconda 3: export PATH=~/anaconda3/bin:$PATH For Anaconda 4: Use the Anaconda Prompt. And then conda –version to confirm that it worked. The export PATH=~/anaconda3/bin:$PATH works, but it stops when you exit the terminal in order change that you have to run sudo nano ~/.bashrc … Read more
That feature has been available since conda v3.8 (after this question was asked). Any *.sh files placed in ${CONDA_PREFIX}/etc/conda/activate.d/ will be sourced when the environment is activated. Docs: https://conda.io/docs/user-guide/tasks/manage-environments.html#saving-environment-variables Also explained here: https://groups.google.com/a/anaconda.com/g/anaconda/c/sQJQ7DBwpfI/m/pP4_Esbl6VYJ
When you type spyder, the search for this command begins in the paths that the conda environment created. If it cannot find it there, it will go and search at other places. In your case in the paths of the default Anaconda install. So after you activate your environment: activate myenv you need to install … Read more