Stream: python-questions

Topic: Fixing corrupt miniconda install

Brian Bonnlander (May 13 2020 at 19:36):

I think I may have corrupted by laptop's miniconda environment by giving a keyboard interrupt during a "conda env create" command. Now when I switch environments, my command prompt does not update, and I am not sure if this is bad. But I can recreate all of my local environments if needed. Any recommendations on how to best fix or reinstall? Is recreating the base environment sufficient? I gave the command conda update -n base, and a bunch of packages including conda were updated successfully, but there is still a problem with the command prompt, and I just want to be safe.

Kevin Paul (May 13 2020 at 19:37):

The problem persists in a new bash shell / terminal window?

Brian Bonnlander (May 13 2020 at 19:37):

Yes.

Kevin Paul (May 13 2020 at 19:37):

Freaky. :half_frown:

Brian Bonnlander (May 13 2020 at 19:38):

It is, kind of. Perhaps it's a superficial problem, but I have no way of knowing if something will bite me later.

Brian Bonnlander (May 13 2020 at 19:40):

Maybe I just download the installer program and clobber the existing install, provided that is not a recipe for disaster.

Kevin Paul (May 13 2020 at 19:42):

What is the output of the following?

conda config --show | grep changeps1

Brian Bonnlander (May 13 2020 at 19:42):

changeps1: False

Kevin Paul (May 13 2020 at 19:43):

That's it. Change it to:

conda config  --set changeps1 True

Brian Bonnlander (May 13 2020 at 19:45):

That did it! I guess it was a superficial symptom. Strange that it would have changed by itself somehow. Maybe that file was being changed when I gave the interrupt.

Kevin Paul (May 13 2020 at 19:45):

Yeah. I'm wondering if that is the case. Could be some other config options were changed at the same time, so keep an eye out.

Last updated: Jan 30 2022 at 12:01 UTC