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

Ensure pip-compile --dry-run --quiet still shows what would be done, while omitting the dry run message #1592

Merged
merged 1 commit into from Apr 4, 2022

Conversation

AndydeCleyre
Copy link
Contributor

@AndydeCleyre AndydeCleyre commented Mar 3, 2022

Fixes #845

Original title: "Ensure pip-compile --dry-run --quiet logs the result (without the dry run message) to stderr"

As the purpose of --dry-run according to our --help docs is to "...show what would happen...", that bit of logging should not be silenced by --quiet, so we herein bypass the log level filtering by using log.log rather than log.info for the output during dry runs.

The corresponding dry+quiet test has been updated accordingly.

I also changed our basic testing of --quiet by removing the --dry-run option and additionally checking that stdout is empty.

Contributor checklist
  • Provided the tests for the changes.
  • Assure PR title is short, clear, and good to be included in the user-oriented changelog
Maintainer checklist
  • Assure one of these labels is present: backwards incompatible, feature, enhancement, deprecation, bug, dependency, docs or skip-changelog as they determine changelog listing.
  • Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

Copy link
Member

@atugushev atugushev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍 Thanks @AndydeCleyre!

@AndydeCleyre AndydeCleyre changed the title Ensure pip-compile --dry-run --quiet logs the result (without the dry run message) to stderr Ensure pip-compile --dry-run --quiet still shows what would be done, while omitting the dry run message Mar 15, 2022
@AndydeCleyre AndydeCleyre force-pushed the bugfix/845 branch 2 times, most recently from 9ed3f82 to 0daecfa Compare April 1, 2022 16:23
@atugushev atugushev added the bug Something is not working label Apr 4, 2022
@atugushev atugushev added this to the 6.6.0 milestone Apr 4, 2022
@atugushev
Copy link
Member

@AndydeCleyre feel free to merge this. I'm going to release this as part of 6.6.0 soon.

- content to stderr
- omit the dry run message

Fixes jazzband#845
@AndydeCleyre
Copy link
Contributor Author

Thanks, I'll merge if the Actions queue ever gets sorted and I get back to this first.

I cancelled unnecessary jobs from my own PRs to clear the way, but the CI queue is in a bad mood today.

@AndydeCleyre AndydeCleyre merged commit 73a8a6e into jazzband:master Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect output on pip-compile upgrade with --dry-run and --quiet flags
2 participants