Thats a bug in conda, you can read more about it here: https://github.com/conda/conda/issues/10969 Right now there is a PR to fix it but its not a released version. For now, just stick with conda install python=3.9
TENSORFLOW 2.0 release version is out! Since 01/10/2019 I’m not talking beta but the release version. Using Anaconda Since 01/11/2019 Anaconda is supporting the Tensorflow 2.0.0. Option 1: For what the easiest way is just: conda install tensorflow or conda install tensorflow-gpu For the gpu mode, anaconda will take care of all the CUDA everything … Read more
A Common Problem: Suboptimal Channel Prioritization Anaconda distribution is designed and tested to use the anaconda channel (a subset of defaults) as its primary channel. Adding conda-forge in either a higher- (channel_priority: strict) or equal-priority (channel_priority: flexible) configuration opens up many of the packages to be sourced from Conda Forge instead, and this is where … Read more
You can simply download google-colab and use it in local. pip install google-colab
Downgrading to conda 4.5.5 fixed this for me. And with a ranting hat on: This is the third time in the space of about 18 months that a conda update has resulted in an error that causes builds to fail, and there’s been plenty of other issues too. I presume it will be fixed by … Read more
This error and the subsequent behaviour is very likely coming from the Anaconda bug which from time to time causes inconsistencies in the local environment. As of Jan 26th, 2020 the bug was not yet resolved. For me the same problem manifests profoundly on Mac.
You want the conda-env command instead, specifically conda env update -n my_env –file ENV.yaml Read the conda env update –help for details. If you wish to install this in the base env, then you would use conda env update -n base –file ENV.yaml Note that the base env isn’t technically “global”, but rather just the … Read more
Although Conda previously did not support PowerShell, this is now resolved in Conda 4.6. After adding Anaconda3/Scripts/ to your PATH variable, you should be able to initialize Conda for use with powershell with: conda init powershell Afterwards, you can use conda normally: conda activate base
I was able to solve a similar situation by removing it using the prefix rather than the name. I.E. conda env remove -p /Users/usr/anaconda3/envs/snowflaks