Closed tamj0rd2 closed 4 years ago
Running these commands solved it. Not sure which one is actually responsible though
sudo pip uninstall virtualenvwrapper
sudo apt-get install virtualenvwrapper
sudo pip install virtualenvwrapper
That makes sense: it would be bad form for a package manager like pip to install things in /etc, which is owned by the system package manager (APT / dpkg). When you use pip install virtualenvwrapper, the config file ends up installed somewhere under your home directory; when you install with apt-get, the config file is installed under /etc.
Thanks. Maybe the steps on the website need to be updated then, since they currently say to use pip
.
I can do a PR for this a bit later
Yes, «sudo pip» leads to trouble and IMO should not be advertised.
I'm currently trying to follow the linux setup steps here. I've followed all of the steps but when I run
source ~/.bash_profile
I get the error/etc/bash_completion.d/virtualenvwrapper: No such file or directory
. Virtualenvwrapper is definitely installed: