-
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
Use log level info when ignoring packages due to environment markers #4877
Conversation
Is there someone who has a spare moment to review this? :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds and looks fine to me.
I'm a little concerned about this. If the user is specifying an extra, via An unavailable extra is an error. Can this be handled in a way that treats failed extra evaluations as errors, but other evaluations as info events? |
Never mind. If the user requests a non-existent extra, the logging takes place at https://github.com/pypa/pip/blob/master/src/pip/_internal/resolve.py#L295. |
The use of environment markers implies that the user expects the packages to not be installed in some cases (eg depending on version of Python), so the log output shouldn't be classed as a warning, particularly since this results in it being sent to `stderr` rather than `stdout`. Fixes #4876.
I've rebased this on master. |
I'd like one more. |
I'm fine with the implementation of the change, but I'm not completely convinced by the argument for why it's needed - It feels correct to me that if we ignore a requirement, that's a warning, not an informational message. But the distinction between warn and info is so subtle in practice, that I don't care a whole lot. So @pradyunsg if you feel OK with switching the level of this message, I'm happy to be your second approval that it's implemented correctly. If you're after approval that the change of level is OK, then I'd say "don't know, but I doubt it's a big deal either way". |
Hi! Thank you for taking a look :-) Can you think of some example use-cases where skipping a requirement really is something of concern that needs a warning on |
(sorry for the terse statement before.) @pfmoore I agree with everything you said. I'm slightly more accepting of this change mostly because I'd prefer spewing less text into stderr for that reason I'm cool with doing a change in level here. |
Many thanks :-) |
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. |
The use of environment markers implies that the user expects the packages to not be installed in some cases (eg depending on version of Python), so the log output shouldn't be classed as a warning, particularly since this results in it being sent to
stderr
rather thanstdout
.Fixes #4876.