Skip to content

--no-clean not working on pip 7.x with vcs install #3171

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
derekstavis opened this issue Oct 9, 2015 · 2 comments
Closed

--no-clean not working on pip 7.x with vcs install #3171

derekstavis opened this issue Oct 9, 2015 · 2 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@derekstavis
Copy link

I have some build scripts which uses pip to install a package from a git repository. The build script installs to a prefix (kind of a virtualenv) and repository's content are used after the install to pick up additional files. With pip 6.x series the following lines does the trick:

    pip install --target=$SITE_PACKAGES \
                --install-option="--install-scripts=$PREFIX_DIR/bin" \
                --build="$BUILD_DIR" \
                --no-deps \
                --no-use-wheel \
                --upgrade \
                --exists-action=i \
                --ignore-installed \
                --no-clean \
                $FULL_REPOSITORY

The behavior of pip 6.x is right: It clones the repository specified by $FULL_REPOSITORY, run the setup.py install and then leave the repository in $BUILD_DIR.

The behavior of pip 7.x, which I see as misleading, is that it removes the repository after running setup.py install, no matter if --no-clean is used or not.

@piotr-dobrogost
Copy link

Could be related to issue #2779

@dstufft
Copy link
Member

dstufft commented Mar 24, 2017

Closing as a duplicate of #2779.

@dstufft dstufft closed this as completed Mar 24, 2017
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 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