Hello community, here is the log from the commit of package python-coverage for openSUSE:Factory checked in at 2017-10-10 11:34:44 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-coverage (Old) and /work/SRC/openSUSE:Factory/.python-coverage.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-coverage" Tue Oct 10 11:34:44 2017 rev:30 rq:531395 version:4.4.1 Changes: -------- --- /work/SRC/openSUSE:Factory/python-coverage/python-coverage.changes 2017-08-14 12:39:44.658324194 +0200 +++ /work/SRC/openSUSE:Factory/.python-coverage.new/python-coverage.changes 2017-10-10 11:35:08.756119552 +0200 @@ -1,0 +2,50 @@ +Wed Oct 4 15:47:22 UTC 2017 - [email protected] + +- update to version 4.4.1: + * No code changes: just corrected packaging for Python 2.7 Linux + wheels. + +- changes from version 4.4: + * Reports could produce the wrong file names for packages, reporting + pkg.py instead of the correct pkg/__init__.py. This is now + fixed. Thanks, Dirk Thomas. + * XML reports could produce <source> and <class> lines that together + didn’t specify a valid source file path. This is now fixed. (issue + 526) + * Namespace packages are no longer warned as having no code. (issue + 572) + * Code that uses sys.settrace(sys.gettrace()) in a file that wasn’t + being coverage-measured would prevent correct coverage measurement + in following code. An example of this was running doctests + programmatically. This is now fixed. (issue 575) + * Errors printed by the coverage command now go to stderr instead of + stdout. + * Running coverage xml in a directory named with non-ASCII + characters would fail under Python 2. This is now fixed. (issue + 573) + +- changes from version 4.4b1: + * Some warnings can now be individually disabled. Warnings that can + be disabled have a short name appended. The [run] disable_warnings + setting takes a list of these warning names to disable. Closes + both issue 96 and issue 355. + * The XML report now includes attributes from version 4 of the + Cobertura XML format, fixing issue 570. + * In previous versions, calling a method that used collected data + would prevent further collection. For example, save(), report(), + html_report(), and others would all stop collection. An explicit + start() was needed to get it going again. This is no longer + true. Now you can use the collected data and also continue + measurement. Both issue 79 and issue 448 described this problem, + and have been fixed. + * Plugins can now find unexecuted files if they choose, by + implementing the find_executable_files method. Thanks, Emil + Madsen. + * Minimal IronPython support. You should be able to run IronPython + programs under coverage run, though you will still have to do the + reporting phase with CPython. + * Coverage.py has long had a special hack to support CPython’s need + to measure the coverage of the standard library tests. This code + was not installed by kitted versions of coverage.py. Now it is. + +------------------------------------------------------------------- Old: ---- coverage-4.3.4.tar.gz New: ---- coverage-4.4.1.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-coverage.spec ++++++ --- /var/tmp/diff_new_pack.kQ4hLi/_old 2017-10-10 11:35:09.384091992 +0200 +++ /var/tmp/diff_new_pack.kQ4hLi/_new 2017-10-10 11:35:09.388091816 +0200 @@ -18,7 +18,7 @@ %{?!python_module:%define python_module() python-%{**} python3-%{**}} Name: python-coverage -Version: 4.3.4 +Version: 4.4.1 Release: 0 Url: http://nedbatchelder.com/code/coverage/%{version} Summary: Code coverage measurement for Python ++++++ coverage-4.3.4.tar.gz -> coverage-4.4.1.tar.gz ++++++ ++++ 6513 lines of diff (skipped)
