Skip to content
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.

User-defined Setup fails with existing Miniconda/Anaconda installation #728

Closed
forman opened this issue Aug 30, 2018 · 2 comments
Closed
Assignees
Milestone

Comments

@forman
Copy link
Member

forman commented Aug 30, 2018

Expected behavior

When Cate's setup dialog pops up during first time installation or during updates users can choose between Automatic setup or User-defined setup. The latter has the option Install in new environment of existing Miniconda/Anaconda installation. It should install Cate as a new Python environment cate-env.

Actual behavior

If User-defined setup / Install in new environment of existing Miniconda/Anaconda installation is used, Cate tries to invoke the Conda activate script in the cate-env environment, which does not exist.

Specifications

Cate 2.0-dev16

@forman forman added this to the IRM10 milestone Aug 30, 2018
@forman forman self-assigned this Aug 30, 2018
@forman
Copy link
Member Author

forman commented Sep 10, 2018

I cannot reproduce the circumstances that would cause this problem to appear. Pausing this.

@forman
Copy link
Member Author

forman commented Sep 11, 2018

Ok, it turned out that during setup, the command

conda env create --name cate-env python=3

fails with error

SpecNotFound: Invalid name, try the format: user/package

The fix is not to use the conda env command but instead just

conda create --name cate-env python=3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant