Hello community, here is the log from the commit of package python-coverage for openSUSE:Factory checked in at 2018-02-12 10:10:54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-coverage (Old) and /work/SRC/openSUSE:Factory/.python-coverage.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-coverage" Mon Feb 12 10:10:54 2018 rev:33 rq:575271 version:4.5 Changes: -------- --- /work/SRC/openSUSE:Factory/python-coverage/python-coverage.changes 2017-11-19 11:10:05.798219488 +0100 +++ /work/SRC/openSUSE:Factory/.python-coverage.new/python-coverage.changes 2018-02-12 10:11:00.302608093 +0100 @@ -1,0 +2,36 @@ +Sat Feb 10 17:25:15 UTC 2018 - [email protected] + +- 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. + +------------------------------------------------------------------- Old: ---- coverage-4.4.2.tar.gz New: ---- coverage-4.5.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-coverage.spec ++++++ --- /var/tmp/diff_new_pack.3bi54D/_old 2018-02-12 10:11:01.166576957 +0100 +++ /var/tmp/diff_new_pack.3bi54D/_new 2018-02-12 10:11:01.166576957 +0100 @@ -1,7 +1,7 @@ # # spec file for package python-coverage # -# Copyright (c) 2017 SUSE LINUX GmbH, Nuernberg, Germany. +# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -18,7 +18,7 @@ %{?!python_module:%define python_module() python-%{**} python3-%{**}} Name: python-coverage -Version: 4.4.2 +Version: 4.5 Release: 0 Url: http://nedbatchelder.com/code/coverage/%{version} Summary: Code coverage measurement for Python ++++++ coverage-4.4.2.tar.gz -> coverage-4.5.tar.gz ++++++ ++++ 2231 lines of diff (skipped)
