Join GitHub today
--no-clean and --build are broken #2060
Pip version 1.5.6
pip install help advertises options:
--no-clean to prevent pip from deleting the build directory and contents, and
and the help for -b says "The default in a virtualenv is "[venv path]/build". The default for global installs is "[OS temp dir]/pip_build_[username]".
On Windows, and from a virtual env, when I run:
pip install -b [some existing path] --no-clean [somepackage].whl
... pip actually uses C:/Users/[me]/AppData/Local/Temp/pip-[random]-build/[packagename] as the build directory, and deletes it when done.
--no-clean is broken
From my not-too-thorough inspection, the problem appears to be that the code that deterimines build path and clean behavior is in req.py, and ignores the no_clean and build_dir settings. Code in install.py that does pay attention to no_clean and build_dir is pre-empted.
I'm assuming that some refactoring of the code broke these features.
I realize that build_dir and no_clean are deprecated (and pip shows a message to that effect), but if they are broken then they should not be reported as deprecated.
Further, issue #906 discusses this deprecation, in which a number of users request that no_clean NOT be removed. I add my vote to that, as it's useful for troubleshooting build steps that went wrong. The current issue that I'm raising is a case in point!
referenced this issue
Sep 23, 2014
it's not broke in linux (using v1.5.6):
can you provide full console output to a gist or a pastebin somewhere that confirms what you're saying.
@qwcode Looks like you figured out what I was reporting, and perhaps it's fixed.