The tox-conda plugin should close that gap nowadays, but needs contributors who actively use conda to test and improve it. from the README: tox-conda is a plugin that provides integration with the conda package and environment manager for the tox automation tool. It’s like having your cake and eating it, too! By default, tox creates … Read more
I would be a bit careful in calling python directly through environment as one never knows if the internals for activate function has changed. I’m just using basic bat-script to help me out. SET log_file=%cd%\logfile.txt call C:\Anaconda3\Scripts\activate.bat cd \script_directory python script.py arg1 arg2 > %log_file% This script saves the log-file wherever the bat is run … Read more
It turns out that the version of libtinfo (installed as part of ncurses) doesn’t provide its version info as suggested in this related answer. I was able to resolve this by forcing ncurses to be installed from the conda-forge channel instead of the default. In my YAML config for my conda env I simply did … Read more
I was able to solve this problem just by running this in a command window with admin privileges: activate <env-name> conda update pip After that, exports of the available packages on my environment contain again both the packages installed with conda and those with pip. I suspect I may have caused this package export problem … Read more
This question was already addressed here, but without a real explanation on the role of prefix. At least there is a solution to exclude the prefix line programmatically. It is not mentioned in the conda doc, except for the fact that conda env export –prefix PATH allows to specify a prefix. But note that –name … Read more
You can “roll back” to a previous revision. First, run: conda list –revisions You will get a list of revisions with their revision number. Then, look at the second-to-last revision and take note of its number. To revert to this revision, run: conda install –revision N where N is the revision number.
You can activate and run a new conda environment in Google Colab by using the magic %%bash command: %%bash source activate myenv python import sys # some simple python commands sys.path.append(‘/usr/local/lib/python3.6/site-packages’) print(sys.path) print(“Python version”) print(sys.version) Also including a few other commands I needed to run to get my environment setup completely: !conda update conda -y … Read more
CONDA_SUBDIR=osx-arm64 conda create -n native numpy -c conda-forge will get you a osx-arm64 native env. To make it permanent, do, conda activate native conda config –env –set subdir osx-arm64
conda create –file environment.yml -n viper won’t work. This command tries to parse every line in the environment.yml as a package name. You should use conda env create –file environment.yml -n viper. Just wait patiently for the conflict resolution to be done.
You just have to refer to the base environment, which is called base and not root: conda create –name <myenv> –clone base