Skip to content
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

Pip build directory clashes if two pip instances are running #1375

Closed
ferrouswheel opened this issue Dec 9, 2013 · 3 comments
Closed

Pip build directory clashes if two pip instances are running #1375

ferrouswheel opened this issue Dec 9, 2013 · 3 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@ferrouswheel
Copy link

We use pip and wheel in our deployment process. If the build server is doing two wheelhouse builds, then the /tmp/pip-build-(user) directory clash and everything goes horribly wrong.

We can use the -b flag to manually specify the build directory, but I feel the user shouldn't have to worry about it.

It seems like this could be fixed by creating a temp dir with tempfile.mkdtemp and using prefix="pip-build-(user)".

@dstufft
Copy link
Member

dstufft commented Dec 9, 2013

This is planned, however it requires deprecating some features. See #906 for some discussion. The required deprecations will happen in 1.5, so it'll be 1.7 or so when this will be able to happen.

@ferrouswheel
Copy link
Author

Thanks for pointing me to it - I was looking for an existing issue but missed that one!

@qwcode
Copy link
Contributor

qwcode commented Dec 9, 2013

I just updated the title for #906 to include mention of mkdtemp dirs. closing this as dupe.

@qwcode qwcode closed this as completed Dec 9, 2013
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 5, 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

3 participants