Update install instructions with conda gcc commands and -p flag #114
Conversation
| @@ -14,8 +14,10 @@ Two popular tools for managing Python environments are `anaconda <https://anacon | |||
|
|
|||
| .. code-block:: bash | |||
|
|
|||
| conda create -y --name environment-name python=3.8 | |||
| conda create -y --name environment-name --prefix full/path/to/environment python=3.8 | |||
There was a problem hiding this comment.
--prefix does not work with --name
It is one of the other. Using prefix is kind of annoying actually, it is better to edit .condarc to avoid having to see the full path to the activated env in terminal window.
There was a problem hiding this comment.
You could list both options -n name OR -p path
There was a problem hiding this comment.
I thought that using the -p option helped sort out CK's conda environment, if so should we just use -p? Or do we think that had more to do with just clearing out whatever was in the old environment, in which case I should go with the easier option (-n)?
There was a problem hiding this comment.
I would list both - it worked for ck because his environment was weird and path based, other's environments may not be.
No description provided.