Closed retiutut closed 3 years ago
I found some instructions that seem similar to what helped me in a currently unused markdown file:
This is very surprising to me. If you ran conda activate "eeg-notebooks"
in the same shell as you later ran pip
then shouldn't that override any system pip install by placing the conda env bin path early in the $PATH
env var? (that's at least how plain venv
and similar behave)
Curious how that wasn't the case. What was the difference that fixed it for you?
@ErikBjare This only happened once, and I would like to try again with a fresh start on a different Mac that already has Python, but not Conda, installed.
I'll report back and close this issue if I am unable to replicate.
Curious how that wasn't the case. What was the difference that fixed it for you?
conda create -n "eeg-notebooks" Python=3
Specifying the python version when creating conda environment was the crucial step that made it work with no issues.
@retiutut Aaah, that makes a lot of sense. Surprised to see conda not pick Python 3 by default.
@retiutut I made a docs PR #51 that should help avoid similar issues in the future.
I tried:
but encountered errors on the last step, since it tried to use my existing python 2 install on my Mac.
@m9h helped me using a different set of instructions.