diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2010-08-24 11:18:35 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2010-08-24 11:18:35 -0400 |
| commit | 9726ca6bbdc7d1ed5b0f732071210eed4ceada34 (patch) | |
| tree | 9bb3969d6654499547cd823d44c3e39a78d57563 /CHANGES.txt | |
| parent | 07d2d57585186c8a6d88dd624a7348a58397f98d (diff) | |
| download | python-coveragepy-git-9726ca6bbdc7d1ed5b0f732071210eed4ceada34.tar.gz | |
New config setting: [report]precision lets you specify the number of digits after the decimal point in coverage percentages. Finishes issue #16.
Diffstat (limited to 'CHANGES.txt')
| -rw-r--r-- | CHANGES.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt index 1af4d9ea..88a28b04 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -10,8 +10,13 @@ Version 3.4b2 percentage is only reported as 0% or 100% if they are truly 0 or 100, and are rounded otherwise. Fixes `issue 41` and issue 70`. +- The precision of reported coverage percentages can be set with the + ``[report] precision`` config file setting. Default is still 0. Completes + ``issue 16``. + .. _issue 70: http://bitbucket.org/ned/coveragepy/issue/70/text-report-and-html-report-disagree-on-coverage .. _issue 41: http://bitbucket.org/ned/coveragepy/issue/41/report-says-100-when-it-isnt-quite-there +.. _issue 16: http://bitbucket.org/ned/coveragepy/issue/16/allow-configuration-of-accuracy-of-percentage-totals Version 3.4b1 --- 21 August 2010 |