You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I usually open a terminal, type su admin, then pip install. This fails because pip tries to create a build directory in the current working directory, which is the home of the user I just su'd away from, where admin had no rights.
(easily worked around by doing cd first)
The funny thing is that this failure gets logged to ~/.pip/pip.log, so why not have the build directory there as well? Or in /tmp?
Sorry if this is necessary for virtualenv, which I know nothing about.
The text was updated successfully, but these errors were encountered:
I usually open a terminal, type
su admin
, thenpip install
. This fails because pip tries to create a build directory in the current working directory, which is the home of the user I just su'd away from, where admin had no rights.(easily worked around by doing
cd
first)The funny thing is that this failure gets logged to ~/.pip/pip.log, so why not have the build directory there as well? Or in /tmp?
Sorry if this is necessary for virtualenv, which I know nothing about.
The text was updated successfully, but these errors were encountered: