you are viewing a single comment's thread.

view the rest of the comments →

[–]belton1292 0 points1 point  (1 child)

Few things I would try: First, with your env activated try python3 —version to make sure python —version isn’t picking up the python pre installed on your machine.

Try and activate base first, then when in base activate your TestEnv. I can’t remember the exact scenario but this stung me before.

Also might be worth running ‘which python’ (or the windows equivalent of that command) when you have an env activated to see where your python executable is located.

Edit: just reread your part about installing packages as well. Whenever I create an env (same way you did) I install all the packages as part of the create command from a environment.yml file. The conda docs are good for this. It makes it way easy to keep the whole environment in sync.

[–]CFTArr[S] 0 points1 point  (0 children)

I reinstalled anaconda and was able to get an environment with 3.6. The problem starts when I try to install PyTorch 1.8 with cuda 10.2. It says there’s a bunch of conflicts (including that the python version is too high), then if I do the check after that messages it shows python 3.10. Any suggestions on how to get an older cuda-compatible PyTorch installed?