My guess is that your pip3 is linked to a non-conda installation of python or somewhere else, while your pip is linked to your conda env’s python 3.6.2
What does your which pip3 and which pip say?
I am also running into this issue when installing Pytorch within an Ubuntu based Singularity container. The container does not make use of Anaconda, so it can’t be a mixup of python paths in my case.
What would happen if we tried going to an older version of torch, say 0.2.0? Would there be any glaring issues there?