Skip to content

Pip should be able to retain the build directory #2053

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
horrovac opened this issue Sep 19, 2014 · 4 comments
Closed

Pip should be able to retain the build directory #2053

horrovac opened this issue Sep 19, 2014 · 4 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@horrovac
Copy link

When a build fails, pip automatically removes all the build files. This should not happen, or there should at least be an option to instruct pip to leave it alone. In many cases the build files provide useful info for troubleshooting, which gets lost for no good reason. Currently, if I want to troubleshoot I have to go find the sources, unpack them somewhere, repeat the build process correctly to reproduce the failure - just to recreate something that was already there. I propose to automatically delete the build files ONLY if the build was successful, otherwise warn and inform the user where the build is. On next run of pip the old build could be automatically deleted or left to the user to take care of. Or: provide a flag, say, --keep-build , which would enable users to request the desirable behaviour.

@dstufft
Copy link
Member

dstufft commented Sep 19, 2014

pip install --no-clean ?

@dstufft dstufft closed this as completed Sep 19, 2014
@dstufft dstufft reopened this Sep 19, 2014
@horrovac
Copy link
Author

Dangit. Perhaps make this request rather "point out pip <action> --help in pip --help". May seem obvious once you know it, but obviously it's not :)

Thanks, that's exactly what I meant.

@gwideman
Copy link

... except that --no-clean doesn't seem to work, as I have now posted in issue #2060.

@qwcode
Copy link
Contributor

qwcode commented Sep 25, 2014

--no-clean is working in most cases. #2060 was really a dupe of #804, which deals with installing directly from local archives.

@horrovac fair point I guess about the help. if you feel strongly about it, log another ticket for that or post a PR with the change in the help text.

closing.

@qwcode qwcode closed this as completed Sep 25, 2014
@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

4 participants