Skip to main content
added 22 characters in body
Source Link
Ben Creasy
  • 460
  • 4
  • 15

I have the exact same setup, and when I pip install virtualenv, the executable symlink is added to /usr/local/bin as expected. So it seems like the install your install is not actually successful.

Did you try using to find or locate to search for virtualenv? Try sudo find / -name virtualenv 2>/dev/null.

Since you're a Python developer, you can load up your favorite debugger or editor (I like Spyder, pudb, PyCharm, and Sublime Text) and debug pip itself. Set a breakpoint (or print statements, whichever) at pip/req/req_install.py:L795. Not far from there it will complete the install by moving the appropriate files.

I have the exact same setup, and when I pip install virtualenv, the executable symlink is added to /usr/local/bin as expected. So it seems like the install is not successful.

Did you try using to find or locate to search for virtualenv? Try sudo find / -name virtualenv 2>/dev/null.

Since you're a Python developer, you can load up your favorite debugger or editor (I like Spyder, pudb, PyCharm, and Sublime Text) and debug pip itself. Set a breakpoint (or print statements, whichever) at pip/req/req_install.py:L795. Not far from there it will complete the install by moving the appropriate files.

I have the exact same setup, and when I pip install virtualenv, the executable symlink is added to /usr/local/bin as expected. So it seems like the install your install is not actually successful.

Did you try using to find or locate to search for virtualenv? Try sudo find / -name virtualenv 2>/dev/null.

Since you're a Python developer, you can load up your favorite debugger or editor (I like Spyder, pudb, PyCharm, and Sublime Text) and debug pip itself. Set a breakpoint (or print statements, whichever) at pip/req/req_install.py:L795. Not far from there it will complete the install by moving the appropriate files.

Source Link
Ben Creasy
  • 460
  • 4
  • 15

I have the exact same setup, and when I pip install virtualenv, the executable symlink is added to /usr/local/bin as expected. So it seems like the install is not successful.

Did you try using to find or locate to search for virtualenv? Try sudo find / -name virtualenv 2>/dev/null.

Since you're a Python developer, you can load up your favorite debugger or editor (I like Spyder, pudb, PyCharm, and Sublime Text) and debug pip itself. Set a breakpoint (or print statements, whichever) at pip/req/req_install.py:L795. Not far from there it will complete the install by moving the appropriate files.