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.

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

consolidate --log and --log-file #915

Closed
qwcode opened this issue Apr 27, 2013 · 0 comments
Closed

consolidate --log and --log-file #915

qwcode opened this issue Apr 27, 2013 · 0 comments
Labels
auto-locked Outdated issues that have been locked by automation C: logging Information Logging kind: backwards incompatible Would be backward incompatible type: enhancement Improvements to functionality

Comments

@qwcode
Copy link
Contributor

qwcode commented Apr 27, 2013

from the 0.7 changelog

"pip now logs to a central location by default (instead of creating pip-log.txt all over the place) and constantly overwrites the file in question. On Unix and Mac OS X this is '$HOME/.pip/pip.log' and on Windows it’s '%HOME%\pip\pip.log'. You are still able to override this location with the $PIP_LOG_FILE environment variable. For a complete (appended) logfile use the separate '--log' command line option"

my biggest problem with this, is that "--log" and "--log-file" mean the same thing (by name) to humans, so it's immediately confusing. it's true that "--log-file" is hidden in the help, but people end up finding it (in order to control it).

Here's the requirements for logging as I see it:

  1. have a consistent default log location (i.e. what we currently use) that can be altered with the one and only log option. (either --log or --log-file, but not both)
  2. have it not append by default (for space issues?), with an option to append (--log-append)
  3. have it honor console --verbosity; (with maybe an optional --log-verbosity if you want different verbosity for logging vs console output)
  4. the console and log file should be logging the same thing; as it is --log-file is only logging when there's errors

related issue: #350

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 5, 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 C: logging Information Logging kind: backwards incompatible Would be backward incompatible type: enhancement Improvements to functionality
Projects
None yet
Development

No branches or pull requests

1 participant