Skip to content

build done in cwd #339

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tewe opened this issue Aug 19, 2011 · 1 comment
Closed

build done in cwd #339

tewe opened this issue Aug 19, 2011 · 1 comment
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@tewe
Copy link

tewe commented Aug 19, 2011

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.

pnasrat added a commit that referenced this issue May 31, 2012
Temporary build and src directories no longer created in cwd/pwd (bugs #339, #381)
@pnasrat
Copy link
Contributor

pnasrat commented May 31, 2012

This should now be fixed in develop.

@pnasrat pnasrat closed this as completed May 31, 2012
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

2 participants