There are python2.7 and python 3.5 in your computer, Jamie.
Sometimes they may be confusing and you are confused who is who. Sometimes you use pip install to install package you don't know you are installing the package to which python. You can use python virtualenv to solve this problem.
Or remember the following:
(a) command 'python2': is for python2.7
(b) command 'python' and 'python3': is for python3.5
(c) the caffe is made by python 2.7
(d) sudo pip install package: will install a package to python2.7
(e) pip3 install package: will install a package to python3.5
I think it's because the position you install python2.7 and ython3.5 determine why you use sudo pip. Using pip will present an error that you have no permission.
There are python2.7 and python 3.5 in your computer, Jamie. Sometimes they may be confusing and you are confused who is who. Sometimes you use pip install to install package you don't know you are installing the package to which python. You can use python virtualenv to solve this problem. Or remember the following: (a) command 'python2': is for python2.7 (b) command 'python' and 'python3': is for python3.5 (c) the caffe is made by python 2.7 (d) sudo pip install package: will install a package to python2.7 (e) pip3 install package: will install a package to python3.5 I think it's because the position you install python2.7 and ython3.5 determine why you use sudo pip. Using pip will present an error that you have no permission.