Hello community, here is the log from the commit of package python3-coverage for openSUSE:Factory checked in at 2016-08-03 11:39:51 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python3-coverage (Old) and /work/SRC/openSUSE:Factory/.python3-coverage.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python3-coverage" Changes: -------- --- /work/SRC/openSUSE:Factory/python3-coverage/python3-coverage.changes 2016-06-02 12:38:16.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.python3-coverage.new/python3-coverage.changes 2016-08-03 11:39:52.000000000 +0200 @@ -1,0 +2,50 @@ +Fri Jul 29 06:02:21 UTC 2016 - [email protected] + +- update to version 4.2: + * BACKWARD INCOMPATIBILITY: the coverage combine command now ignores + an existing .coverage data file. It used to include that file in + its combining. This caused confusing results, and extra tox + “clean” steps. If you want the old behavior, use the new coverage + combine --append option. + * Since concurrency=multiprocessing uses subprocesses, options + specified on the coverage.py command line will not be communicated + down to them. Only options in the configuration file will apply to + the subprocesses. Previously, the options didn’t apply to the + subprocesses, but there was no indication. Now it is an error to + use --concurrency=multiprocessing and other run-affecting options + on the command line. This prevents failures like those reported in + issue 495. + * The concurrency option can now take multiple values, to support + programs using multiprocessing and another library such as + eventlet. This is only possible in the configuration file, not + from the command line. The configuration file is the only way for + sub-processes to all run with the same options. Fixes issue + 484. Thanks to Josh Williams for prototyping. + * Using a concurrency setting of multiprocessing now implies + --parallel so that the main program is measured similarly to the + sub-processes. + * When using automatic subprocess measurement, running coverage + commands would create spurious data files. This is now fixed, + thanks to diagnosis and testing by Dan Riti. Closes issue 492. + * A new configuration option, report:sort, controls what column of + the text report is used to sort the rows. Thanks to Dan + Wandschneider, this closes issue 199. + * The HTML report has a more-visible indicator for which column is + being sorted. Closes issue 298, thanks to Josh Williams. + * Filtering the HTML report is now faster, thanks to Ville Skyttä. + * If the HTML report cannot find the source for a file, the message + now suggests using the -i flag to allow the report to + continue. Closes issue 231, thanks, Nathan Land. + * When reports are ignoring errors, there’s now a warning if a file + cannot be parsed, rather than being silently ignored. Closes issue + 396. Thanks, Matthew Boehm. + * A new option for coverage debug is available: coverage debug + config shows the current configuration. Closes issue 454, thanks + to Matthew Boehm. + * Running coverage as a module (python -m coverage) no longer shows + the program name as __main__.py. Fixes issue 478. Thanks, Scott + Belden. + * The test_helpers module has been moved into a separate + pip-installable package: unittest-mixins. + +------------------------------------------------------------------- Old: ---- coverage-4.1.tar.gz New: ---- coverage-4.2.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python3-coverage.spec ++++++ --- /var/tmp/diff_new_pack.jzDLW8/_old 2016-08-03 11:39:53.000000000 +0200 +++ /var/tmp/diff_new_pack.jzDLW8/_new 2016-08-03 11:39:53.000000000 +0200 @@ -17,7 +17,7 @@ Name: python3-coverage -Version: 4.1 +Version: 4.2 Release: 0 Url: http://nedbatchelder.com/code/coverage/%{version} Summary: Code coverage measurement for Python ++++++ coverage-4.1.tar.gz -> coverage-4.2.tar.gz ++++++ ++++ 5687 lines of diff (skipped)
