Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package python-coverage for openSUSE:Factory
checked in at 2026-03-17 19:02:04
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-coverage (Old)
and /work/SRC/openSUSE:Factory/.python-coverage.new.8177 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-coverage"
Tue Mar 17 19:02:04 2026 rev:74 rq:1339133 version:7.13.4
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-coverage/python-coverage.changes
2026-02-11 18:47:35.426209929 +0100
+++
/work/SRC/openSUSE:Factory/.python-coverage.new.8177/python-coverage.changes
2026-03-17 19:02:08.238815858 +0100
@@ -1,0 +2,146 @@
+Sun Mar 15 15:14:51 UTC 2026 - Dirk Müller <[email protected]>
+
+- update to 7.13.4:
+ * Fix: the third-party code fix in 7.13.3 required examining
+ the parent directories where coverage was run. In the unusual
+ situation that one of the parent directories is unreadable, a
+ PermissionError would occur, as described in issue 2129. This
+ is now fixed.
+ * Fix: in test suites that change sys.path, coverage.py could
+ fail with "RuntimeError: Set changed size during iteration"
+ as described and fixed in pull 2130. Thanks, Noah Fatsi.
+ * We now publish ppc64le wheels, thanks to Pankhudi Jain.
+ * Fix: in some situations, third-party code was measured when
+ it shouldn't have been, slowing down test execution. This
+ happened with layered virtual environments such as uv
+ sometimes makes. The problem is fixed, closing issue 2082.
+ Now any directory on sys.path that is inside a virtualenv is
+ considered third-party code.
+ * Fix: when Python is installed via symlinks, for example with
+ Homebrew, the standard library files could be incorrectly
+ included in coverage reports. This is now fixed, closing
+ issue 2115.
+ * Fix: if a data file is created with no read permissions, the
+ combine step would fail completely. Now a warning is issued
+ and the file is skipped. Closes issue 2117.
+ * Added: the JSON report now includes a "start_line" key for
+ function and class regions, indicating the first line of the
+ region in the source. Closes issue 2110.
+ * Added: The debug data command now takes file names as
+ arguments on the command line, so you can inspect specific
+ data files without needing to set the COVERAGE_FILE
+ environment variable.
+ * Fix: the JSON report used to report module docstrings as
+ executed lines, which no other report did, as described in
+ issue 2105. This is now fixed, thanks to Jianrong Zhao.
+ * Fix: coverage.py uses a more disciplined approach to
+ detecting where third-party code is installed, and avoids
+ measuring it. This shouldn't change any behavior. If you find
+ that it does, please get in touch.
+ * Performance: data files that will be combined now record
+ their hash as part of the file name. This lets us skip
+ duplicate data more quickly, speeding the combining step.
+ * Docs: added a section explaining more about what is
+ considered a missing branch and how it is reported:
+ :ref:`branch_explain`, as requested in issue 1597. Thanks to
+ Ayisha Mohammed.
+ * Tests: the test suite misunderstood what core was being
+ tested if COVERAGE_CORE wasn't set on 3.14+. This is now
+ fixed, closing issue 2109.
+ * Feature: coverage.py now supports :file:`.coveragerc.toml`
+ configuration files. These files use TOML syntax and take
+ priority over :file:`pyproject.toml` but lower priority than
+ :file:`.coveragerc` files. Closes issue 1643 thanks to Olena
+ Yefymenko.
+ * Fix: we now include a permanent .pth file which is installed
+ with the code, fixing issue 2084. In 7.12.1b1 this was done
+ incorrectly: it didn't work when using the source wheel
+ (py3-none-any). This is now fixed. Thanks, Henry Schreiner.
+ * Deprecated: when coverage.py is installed, it creates three
+ command entry points: coverage, coverage3, and coverage-3.10
+ (if installed for Python 3.10). The second and third of these
+ are not needed and will eventually be removed. They still
+ work for now, but print a message about their deprecation.
+ * Fix: coverage.py now includes a permanent .pth file in the
+ distribution which is installed with the code. This fixes
+ issue 2084: failure to patch for subprocess measurement when
+ site-packages is not writable.
+ * The HTML report now shows separate coverage totals for
+ statements and branches, as well as the usual combined
+ coverage percentage. Thanks to Ryuta Otsuka for the
+ discussion and the implementation.
+ * The JSON report now includes separate coverage totals for
+ statements and branches, thanks to Ryuta Otsuka.
+ * Fix: except* clauses were not handled properly under the
+ "sysmon" measurement core, causing KeyError exceptions as
+ described in issue 2086. This is now fixed.
+ * Fix: we now defend against aggressive mocking of open() that
+ could cause errors inside coverage.py. An example of a
+ failure is in issue 2083.
+ * Fix: in unusual cases where a test suite intentionally
+ exhausts the system's file descriptors to test handling
+ errors in open(), coverage.py would fail when trying to open
+ source files, as described in issue 2091. This is now fixed.
+ * A small tweak to the HTML report: file paths now use thin
+ spaces around slashes to make them easier to read.
+ * Fix: the 7.11.1 changes meant that conflicts between a
+ requested measurement core and other settings would raise an
+ error. This was a breaking change from previous behavior, as
+ reported in issue 2076 and issue 2078. The previous behavior
+ has been restored: when the requested core conflicts with
+ other settings, another core is used instead, and a warning
+ is issued.
+ * For contributors: the repo has moved from Ned's nedbat GitHub
+ account to the coveragepy GitHub organization. The default
+ branch has changed from master to main.
+ * Fix: using the "sysmon" measurement core in 7.11.1, if Python
+ code was claimed to come from a non-Python file, a NotPython
+ exception could be raised. This could happen for example with
+ Jinja templates compiled to Python, as reported in issue
+ 2077. This is now fixed.
+ * Doc: corrected the first entry in the 7.11.1 changelog.
+ * Fix: some chanages to details of how the measurement core is
+ chosen, and how conflicting settings are handled. The
+ "sysmon" core cannot be used with some conurrency settings,
+ with dynamic context, and in Python 3.12/3.13, with branch
+ measurement. If the core is not specified and defaults to
+ "sysmon" (Python 3.14+), but other settings conflict with
+ sysmon, then the "ctrace" core will be used instead with no
+ warning. For concurrency conflicts, this used to produce an
+ error, as described in issue 2064. If the "sysmon" core is
+ explicitly requested in your configuration, but other
+ settings conflict, an error is now raised. This used to
+ produce a warning.
+ * If the core is not specified and defaults to "sysmon" (Python
+ 3.14+), but other settings conflict with sysmon, then the
+ "ctrace" core will be used instead with no warning. For
+ concurrency conflicts, this used to produce an error, as
+ described in issue 2064.
+ * If the "sysmon" core is explicitly requested in your
+ configuration, but other settings conflict, an error is now
+ raised. This used to produce a warning.
+ * Fix: some multi-line case clauses or for loops (and probably
+ other constructs) could cause incorrect claims of missing
+ branches with the sys.monitoring core, as described in issue
+ 2070. This is now fixed.
+ * Fix: when running in pytest under coverage, a breakpoint()
+ would stop in the wrong frame, one level down from where it
+ should, as described in issue 1420. This was due to a
+ coverage change in v6.4.1 that seemed to give a slight
+ performance improvement, but I couldn't reproduce the
+ performance gain, so it's been reverted, fixing the debugger
+ problem.
+ * A new debug option --debug=core shows which core is in use
+ and why.
+ * Split sqlite debugging information out of the sys
+ :ref:`coverage debug <cmd_debug>` and :ref:`cmd_run_debug`
+ options since it's bulky and not very useful.
+ * Updated the :ref:`howitworks` page to better describe the
+ three different measurement cores.
+ * Dropped support for Python 3.9, declared support for Python
+ 3.15 alpha.
+- Drop string.patch (upstream).
+- Update BuildRequires for python-devel and pytest to match
+ upstream requirements.
+
+-------------------------------------------------------------------
Old:
----
coverage-7.10.7.tar.gz
string.patch
New:
----
coverage-7.13.4.tar.gz
----------(Old B)----------
Old: 3.15 alpha.
- Drop string.patch (upstream).
- Update BuildRequires for python-devel and pytest to match
----------(Old E)----------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-coverage.spec ++++++
--- /var/tmp/diff_new_pack.QXx6VZ/_old 2026-03-17 19:02:10.314900993 +0100
+++ /var/tmp/diff_new_pack.QXx6VZ/_new 2026-03-17 19:02:10.330901649 +0100
@@ -33,15 +33,13 @@
%{?sle15_python_module_pythons}
Name: python-coverage%{psuffix}
-Version: 7.10.7
+Version: 7.13.4
Release: 0
Summary: Code coverage measurement for Python
License: Apache-2.0
URL: https://github.com/nedbat/coveragepy
Source:
https://files.pythonhosted.org/packages/source/c/coverage/coverage-%{version}.tar.gz
-# PATCH-FIX-UPSTREAM
https://github.com/coveragepy/coveragepy/commit/cf95edab0c3be47ab934f0425f12743745dd2da5
test: a Python error message changed slightly
-Patch0: string.patch
-BuildRequires: %{python_module devel >= 3.9}
+BuildRequires: %{python_module devel >= 3.10}
BuildRequires: %{python_module pip}
BuildRequires: %{python_module setuptools}
BuildRequires: %{python_module wheel}
@@ -62,9 +60,9 @@
# SECTION test requirements
BuildRequires: %{python_module coverage = %{version}}
BuildRequires: %{python_module flaky}
-BuildRequires: %{python_module hypothesis >= 6}
+BuildRequires: %{python_module hypothesis >= 6.150}
+BuildRequires: %{python_module pytest >= 9.0.0}
BuildRequires: %{python_module pytest-xdist}
-BuildRequires: %{python_module pytest}
BuildRequires: %{python_module tomli}
# for database (sqlite3) support
BuildRequires: %{pythons}
@@ -80,9 +78,6 @@
%prep
%autosetup -p1 -n coverage-%{version}
-# we define everything necessary ourselves below
-sed -i -e '/addopts/d' setup.cfg
-
%build
%if %{without test}
%pyproject_wheel
@@ -121,7 +116,7 @@
$mypython igor.py zip_mods
# test_version - checks for non-compiled variant, we ship only compiled one
-donttest="test_version"
+donttest="test_version or test_core"
# test_xdist_sys_path_nuttiness_is_fixed - xdist check that we actually fail
on purpose
donttest+=" or test_xdist_sys_path_nuttiness_is_fixed"
# does not find a usable venv
@@ -157,5 +152,6 @@
%python_alternative %{_bindir}/coverage
%{python_sitearch}/coverage/
%{python_sitearch}/coverage-%{version}.dist-info
+%{python_sitearch}/a1_coverage.pth
%endif
++++++ coverage-7.10.7.tar.gz -> coverage-7.13.4.tar.gz ++++++
++++ 28684 lines of diff (skipped)
