-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Should we print an error if --user and --target are used together? #7249
Labels
auto-locked
Outdated issues that have been locked by automation
C: target
pip install's --target option's behaviour handling
C: user scheme
Handling of packages in user-specific directories
state: awaiting PR
Feature discussed, PR is needed
type: enhancement
Improvements to functionality
Comments
triage-new-issues
bot
added
the
S: needs triage
Issues/PRs that need to be triaged
label
Oct 21, 2019
If I try passing both, I get an error from distutils. It's pretty clear, so maybe this is why it's not checked in pip, but maybe it still makes sense to check it and fail faster.
|
chrahunt
added
C: target
pip install's --target option's behaviour handling
C: user scheme
Handling of packages in user-specific directories
state: needs discussion
This needs some more discussion
type: enhancement
Improvements to functionality
labels
Oct 21, 2019
triage-new-issues
bot
removed
the
S: needs triage
Issues/PRs that need to be triaged
label
Oct 21, 2019
chrahunt
added
state: awaiting PR
Feature discussed, PR is needed
and removed
state: needs discussion
This needs some more discussion
labels
Nov 10, 2019
This seems pretty straightforward, so changing status. |
@pradyunsg I am on it. 👍 |
lock
bot
added
the
auto-locked
Outdated issues that have been locked by automation
label
Apr 2, 2020
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
C: target
pip install's --target option's behaviour handling
C: user scheme
Handling of packages in user-specific directories
state: awaiting PR
Feature discussed, PR is needed
type: enhancement
Improvements to functionality
No clue. Filing a new issue to track someone figuring this out. :)
Originally posted by @chrahunt in #7002
The text was updated successfully, but these errors were encountered: