Skip to content

Update install instructions with conda gcc commands and -p flag #114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

Update install instructions with conda gcc commands and -p flag #114

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/install.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

--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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could list both options -n name OR -p path

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would list both - it worked for ck because his environment was weird and path based, other's environments may not be.

conda activate environment-name
conda install gcc_linux-64 (or distro appropriate package)
conda install gxx_linux-64 (or distro appropriate package)

and using venv:

Expand Down