python/python-coverage
SHA256
14
0
Fork 0
forked from pool/python-coverage
Code Pull Requests Activity

Accepting request 575253 from home:apersaud:branches:devel:languages:python

Browse Source 
update to latest version

OBS-URL: https://build.opensuse.org/request/show/575253
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-coverage?expand=0&rev=67
This commit is contained in:
Tomáš Chvátal
2018-02-10 19:40:41 +00:00
committed by Git OBS Bridge
parent d78d571e05
commit 309dae557c
4 changed files with 41 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
python-coverage.changes
View File

@@ -1,3 +1,39 @@
-------------------------------------------------------------------
Sat Feb 10 17:25:15 UTC 2018 - arun@gmx.de
- specfile:
* update copyright year
- update to version 4.5:
* A new kind of plugin is supported: configurators are invoked at
start-up to allow more complex configuration than the .coveragerc
file can easily do. See Plug-in classes for details. This solves
the complex configuration problem described in issue 563.
* The fail_under option can now be a float. Note that you must
specify the [report] precision configuration option for the
fractional part to be used. Thanks to Lars Hupfeldt Nielsen for
help with the implementation. Fixes issue 631.
* The include and omit options can be specified for both the [run]
and [report] phases of execution. 4.4.2 introduced some incorrect
interactions between those phases, where the options for one were
confused for the other. This is now corrected, fixing issue 621
and issue 622. Thanks to Daniel Hahler for seeing more clearly
than I could.
* The coverage combine command used to always overwrite the data
file, even when no data had been read from apparently combinable
files. Now, an error is raised if we thought there were files to
combine, but in fact none of them could be used. Fixes issue 629.
* The coverage combine command could get confused about path
separators when combining data collected on Windows with data
collected on Linux, as described in issue 618. This is now fixed:
the result path always uses the path separator specified in the
[paths] result.
* On Windows, the HTML report could fail when source trees are
deeply nested, due to attempting to create HTML filenames longer
than the 250-character maximum. Now filenames will never get much
larger than 200 characters, fixing issue 627. Thanks to Alex
Sandro for helping with the fix.
-------------------------------------------------------------------
Thu Nov 9 19:10:43 UTC 2017 - jmatejek@suse.com