No module named conda.cli.main #2463
Comments
|
Definitely looks like a bug on our part. Conda should never take actions that will cripple itself. You may be able to repair things using this strategy: Can you see if you can figure out the conda version you were using that caused this problem? import conda
conda.__version__if it is importable. And if not, maybe cat /username/anaconda/lib/python2.7/site-packages/conda/__init__.py |
|
Hah, glad I read this earlier today, because moments ago this happened to me (using conda v4.0.5). Observe in trace below: So this successfully created a new environment, but then when I went to activate it: Nutty! So then I tried to investigate further: It's like @kalefranz is this resolved by 4.0.6? |
|
A little bit more investigating: |
|
Even tried using |
kalefranz
added
the
type::bug
|
@ijstokes Regarding errors you posted above, I was unable to reproduce using conda version 4.0.5 |
kalefranz
added
source::community
|
@ijstokes Believe it or not, a fix to some of this stuff with conda crippling itself actually touches on some of the configuration issues we've been discussing. There's a configuration ticket marked for the 4.3 milestone, but it'll probably end up being part of 4.2. |
|
This might occur when the user name in the path on windows contains a space character. |
|
Setting the PATH as noted in this stack overflow post resolved this issue for me. |
|
@ijstokes Were you able to find a workaroung for the issue under Cloudera? I am having the same problem with the Anaconda CDH 4.1.1 parcel (although |
|
I believe this is due to the fact that Anaconda's python is no longer in |
|
My colleague encountered the same error today. It turns out that it is caused by an empty file named However, I cannot reproduce the problem on my box. Even if I upgrade to |
|
Guys, I recently encountered this problem and I found why My original anaconda installation is anaconda 3 with python3.6. And I configure the conda source to a mirror close to me. Recently I installed a new package to the base environment. The conda command promoted that python3.7 along with other packages will be downloaded and installed. Then I realized the conflict may come from a different source, when setting the source of conda, conda-forge was moved to the top and has higher priority that the main conda channel. Then the python3.7 and other packages are from conda-forge and may have a conflict with existing packages. Hope this will help |
Thanks for your answer! Could you show us an explicit example of you've done?. I've got the same problem I'm really lost to solve it just reading all answers Thanks in advance! |
Hi @felio333
After that I had some issues like reinstalling some packages in the environment I use, but conda works fine |
Seem still not clear, since I have many envs before. When reinstall a new conda, only move these envs enough? "replacing all files when needed" you said not means move any one of condas? Thank but I move envs only works, but pkgs in base yes still empty and this is a small question. |
|
Finally, since this problem was discovered when I reinstalled the spyder, it is still impossible to reinstall the spyder in env "base" even after the above work. I have not solved this problem, so I input conda install spyder again in "base" and found that python3.7 will be installed again, so I gave up. |
|
for the Cloudera folks.... changing the shebang in /opt/cloudera/parcels/Anaconda/bin/conda worked for me |
|
Just update conda to compatible with python works for me |
this works for me, thank you. |
|
I tried all the steps above but couldnt resolve the issue. However this worked for me . |
It could be a conflict between Python in Conda with system Python, or between multiple conda.First, you can check the $PATH, $PYTHONPATH, $PYTHONHOME, $LD_LIBRARY_PATH, and $LIBRARY_PATH in <your home>/.bashrc file to make sure there is only one python and python library from conda directory.There maybe the other similar file to .bashrc file in your systerm. Second, add <your conda>/bin to the $PATH.Third, restart the system or re-enter your server.Maybe source <your home>/.bashrc is OK, but in my server it is OK for re-entering the server. Finally, try conda --help.It resolves the problem. |
|
On Windows : go to "System Properties" -> "Environment Variables" -> clear value of "PYTHONPATH" |
|
I think this answer should be considered in Anaconda. You will inevitably break your conda when you upgrade anaconda and some package triggers a python version change. |
|
Hi there, thank you for your contribution to Conda! This issue has been automatically locked since it has not had recent activity after it was closed. Please open a new issue if needed. |
Hi all, I encountered problem with conda after I updated packages
After executing
conda update --all, I freed up some spaces withconda clean -pityIt is similar to issue #2200
I checked the root environment directory and found that some symbolic link files are broken, eg. activate, deactivate
Those files are pointed to conda .pkgs directory, which was cleaned with
conda clean -pityAny ideas how to recover it, or reinstall
conda?The text was updated successfully, but these errors were encountered: