![]() ![]() You are using pip version 6.1.1, however version 9.0.1 is available. Install the version of virtualenv packaged with the version of pip you are looking to upgrade to to the system-level pip (e.g. If you're OK with that, here's the basic idea: I think the best strategy in this case is to manage pip is as part of a virtual environment using virtualenv rather than messing with the system-level version. ![]() Another alternative, if you'd prefer to not add that path to your secure_path is to make a symbolic link to the new pip executable in /usr/bin. You can add this path to the secure_path variable by running sudo visudo. Not entirely clear on where the name translation from pip to pip-2.7 occurs.Īs mentioned in another answer, pip now exists in /usr/local/bin after the upgrade, which is no longer in the sudo secure path. So, that's where our error comes from, as the upgrade clearly doesn't clean this file up. # EASY-INSTALL-ENTRY-SCRIPT: 'pip=6.1.1','console_scripts','pip2.7'įrom pkg_resources import load_entry_point However, what remains is a file called pip-27, which contains the following: #!/usr/bin/python2.7 The reason sudo pip stops working after the upgrade, is because the executable (or symbolic link) is removed from /usr/bin. Entering root with sudo su - allows pip to be run without issue.This is actually okay, since in most cases, pip installs fail when not run as root anyway. ec2_user finds the pip executable, but has a module import error due to other having no read/execute permissions on the pip folders in the /usr/local/lib/python2.7/site-packages folder.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |