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.

Sign up for GitHub

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

Jump to bottom

pip install --target option incompitable with other options #1833

Closed
richburdon opened this issue May 23, 2014 · 8 comments
Closed

pip install --target option incompitable with other options #1833

richburdon opened this issue May 23, 2014 · 8 comments
Labels
auto-locked Outdated issues that have been locked by automation C: target pip install's --target option's behaviour handling

Comments

@richburdon
Copy link

The -t option seems to break other options used with pip install.

1). with --upgrade -r requirements.txt
Error: Destination path '...' already exists (i.e., --upgrade seems to be ignored)

2). with -e git+git@github.com:.../foo.git#egg=foo
error: option --home not recognized
@webmaven
Copy link

Related to #1489 and #1710.

@webmaven webmaven mentioned this issue Jul 10, 2014
Closed
theacodes added a commit to theacodes/pip that referenced this issue Aug 31, 2014
@theacodes
Fixing issues with install's --target option.
acf8634 
 1. Check for the existence of a directory before copying from temporary directory to final target. If it exists, warn the user.
 2. If the user specifies the --upgrade option and the directory exists, delete it and continue with installation.
 3. Adding tests for above cases.

This resolves pypa#1489, pypa#1710 completely and parts of pypa#1833.
@theacodes theacodes mentioned this issue Aug 31, 2014
Merged
@ergodicbreak ergodicbreak mentioned this issue Jun 22, 2015
Closed
@xavfernandez xavfernandez added the C: target pip install's --target option's behaviour handling label Oct 20, 2015
@singpolyma
Copy link

I seem to be encountering issue 2 -- when I use -t and my requirements.txt contains a -e for git, it breaks

@jonathan-s
Copy link

I also encounter issue 2. Is there a workaround for this?

@abesmon
Copy link

abesmon commented Aug 2, 2016

also have problems with issue 2. IT`s 2 years since issue :D

@webmaven
Copy link

webmaven commented Sep 17, 2016 •
edited
Loading

ping @dstufft + @pfmoore

@dstufft
Copy link
Member

dstufft commented Mar 30, 2017

Closing this as one of the issues is solved, and the other issue is better explained in #4106.

@dstufft dstufft closed this as completed Mar 30, 2017
@webmaven
Copy link

webmaven commented Dec 24, 2017 •
edited
Loading

For those following along from home, the ＃4106 issue was subsequently merged into #4390.

@hrkfdn hrkfdn mentioned this issue Jul 6, 2018
Merged
@lock
Copy link

lock bot commented Jun 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 2, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-locked Outdated issues that have been locked by automation C: target pip install's --target option's behaviour handling
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@singpolyma @dstufft @webmaven @xavfernandez @jonathan-s @richburdon @abesmon