cannot get spacy properly installed to use GPU because of conflict with pytorch or cupy or thinc #7633
Replies: 3 comments 1 reply
-
Futher to this: I uninstalled python from my windows 10 PC, by removing anaconda totally, then rebooted, then run Anaconda3-2020.11-Windows-x86_64.exe, then did
the update did this (among many other things): scipy pkgs/main::scipy-1.5.2-py38h14eb087_0 --> conda-forge::scipy-1.6.2-py38he847743_0 then
fixed by the
did not fixed it. |
Beta Was this translation helpful? Give feedback.
-
Also
installs pytorch but the CPU version I think and does not allow spacy to access GPU anymore, as spacy seems to stop using thinc and start using pytorch as backend? So this combination does not work for GPU:
|
Beta Was this translation helpful? Give feedback.
-
Thanks. Yes, mixing conda and pip is not good, but I think spacy-transformers and spacy-lookups-data doesn't exist in conda yet. I may try to do the following whenever I redo my installations of python from fresh, forcing pytorch cuda11.2 before I actually install the rest:
|
Beta Was this translation helpful? Give feedback.
-
Hi
I have a Windows 10 PC with card is NVIDIA GeForce RTX 2060
Compute capability 7.5
CUDA SDK 11.0 – 11.2 support for compute capability 3.5 – 8.6
I had to do a fresh install, so removed anaconda totally, reboot, reinstalled anaconda Anaconda3-2020.11-Windows-x86_64.exe, then did
Then I see this:
Then I did
Then I see this:
while this works:
So spacy only works if I import torch first? Why? In my previous installation all was working, pytorch, thinc, spacy, but I forgot the conda/pip sequence I used then before rebuilding the PC.
So question is what is the right sequence of installs for a Windows 10 PC with card is NVIDIA GeForce RTX 2060 and Cuda compilation tools, release 11.0, V11.0.221
Build cuda_11.0_bu.relgpu_drvr445TC445_37.28845127_0 ?
Thanks
Eurico
Beta Was this translation helpful? Give feedback.
All reactions