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

Log removal of bdist_dir always instead of just during a dry run #199

Merged
merged 1 commit into from
Oct 29, 2017
Merged

Log removal of bdist_dir always instead of just during a dry run #199

merged 1 commit into from
Oct 29, 2017

Conversation

rytilahti
Copy link
Contributor

When trying to help debugging a build of a package made by someone else I got confused as there was no indicated files available under the bdist directory. This PR just moves the log message to be displayed even when no --dry-run is defined to avoid such confusions in the future.

@codecov
Copy link

codecov bot commented Oct 17, 2017

Codecov Report

Merging #199 into master will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #199   +/-   ##
=======================================
  Coverage   69.86%   69.86%           
=======================================
  Files          18       18           
  Lines        1815     1815           
=======================================
  Hits         1268     1268           
  Misses        547      547
Impacted Files Coverage Δ
wheel/bdist_wheel.py 56.77% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c8f23fe...acd75c9. Read the comment docs.

@agronholm agronholm merged commit 3a87ece into pypa:master Oct 29, 2017
@agronholm
Copy link
Contributor

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants