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-08-15 22:39:37
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-coverage (Old)
and /work/SRC/openSUSE:Factory/.python-coverage.new.1258 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-coverage"
Sat Aug 15 22:39:37 2026 rev:77 rq:1371095 version:7.14.3
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-coverage/python-coverage.changes
2026-06-13 18:46:49.032132538 +0200
+++
/work/SRC/openSUSE:Factory/.python-coverage.new.1258/python-coverage.changes
2026-08-15 22:39:42.137635157 +0200
@@ -1,0 +2,65 @@
+Thu Aug 6 19:59:15 UTC 2026 - Dirk Müller <[email protected]>
+
+- update to 7.14.3:
+ * Fix: the default ... exclusion rule now also matches function
+ bodies whose closing return-type bracket is on its own line
+ (for example, after a long -> dict[ ... ] annotation that a
+ formatter has split over multiple lines). Closes issue 2185,
+ thanks Mengjia Shang.
+ * Fix: On 3.13t, we incorrectly issued Couldn't import C tracer
+ errors. We can't import the C tracer because in 7.14.2 we
+ stopped shipping compiled wheels for 3.13t. Thanks, Hugo van
+ Kemenade.
+ * Fix: some messages were being written to stdout, making
+ coverage json -o - useless for capturing JSON output. Now
+ messages are written to stderr, fixing issue 2197.
+ * Fix: CoverageData kept one SQLite connection per thread that
+ recorded coverage, but never closed them when those threads
+ terminated. On long runs with many short-lived threads this
+ leaked one file descriptor per dead thread, eventually
+ failing with OSError: [Errno 24] Too many open files.
+ Connections belonging to terminated threads are now closed
+ and dropped. Fixes issue 2192. Thanks, Matthew Lloyd.
+ * Fix: when using sys.monitoring, we were assuming we could use
+ the COVERAGE_ID tool id. But other tools might also assume
+ they could use that id. Pre-allocated ids don't really make
+ sense, so now we search for a usable one instead. Fixes issue
+ 2187.
+ * Following the advice of cibuildwheel, we no longer distribute
+ wheels for Python 3.13 free-threaded.
+ * Fix: the HTML report used typographic niceties to make file
+ paths more readable by adding a small amount of space around
+ slashes. Those spaces interfered with searching the page for
+ file paths of interest. Now the report uses CSS to accomplish
+ the same visual tweak so that searches with slashes work
+ correctly. Closes issue 2170.
+ * Add a 3.16 PyPI classifier since we test on the 3.16 main
+ branch.
+ * Feature: now when running one of the reporting commands, if
+ there are parallel data files that need combining, they will
+ be implicitly combined before creating the report. There is
+ no option to avoid the combination; let us know if you have a
+ use case that requires it. Thanks, Tim Hatch. Closes issue
+ 1781.
+ * Fix: the output from combine was too verbose, listing each
+ file considered. Now it shows a single line with the counts
+ of files combined, files skipped, and files with errors. The
+ -q flag suppresses this line. The old detailed lines are
+ available with the new --debug=combine option.
+ * Fix: running a Python file through a symlink now sets the
+ sys.path correctly, matching regular Python behavior. Fixes
+ issue 2157.
+ * Fix: Collector.flush_data could fail with "RuntimeError: Set
+ changed size during iteration" when a tracer in another
+ thread added a line to the per-file set that add_lines (or
+ add_arcs) was iterating. The values passed to CoverageData
+ are now snapshotted via dict.copy() and set.copy(), which are
+ atomic under the GIL. Thanks, Alex Vandiver.
+ * Fix: the soft keyword lazy is now bolded in HTML reports.
+ * We are no longer testing eventlet support. Eventlet started
+ issuing stern deprecation warnings that break our tests. Our
+ support code is still there.
+- drop fix-set-sys.path-correctly-when-running-through-a-sy.patch
+ (upstream)
+
+-------------------------------------------------------------------
Old:
----
coverage-7.13.5.tar.gz
fix-set-sys.path-correctly-when-running-through-a-sy.patch
New:
----
coverage-7.14.3.tar.gz
----------(Old B)----------
Old: support code is still there.
- drop fix-set-sys.path-correctly-when-running-through-a-sy.patch
(upstream)
----------(Old E)----------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-coverage.spec ++++++
--- /var/tmp/diff_new_pack.ATQboy/_old 2026-08-15 22:39:42.855660438 +0200
+++ /var/tmp/diff_new_pack.ATQboy/_new 2026-08-15 22:39:42.857660508 +0200
@@ -33,13 +33,12 @@
%{?sle15_python_module_pythons}
Name: python-coverage%{psuffix}
-Version: 7.13.5
+Version: 7.14.3
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
-Patch0: fix-set-sys.path-correctly-when-running-through-a-sy.patch
BuildRequires: %{python_module devel >= 3.10}
BuildRequires: %{python_module pip}
BuildRequires: %{python_module setuptools}
++++++ coverage-7.13.5.tar.gz -> coverage-7.14.3.tar.gz ++++++
++++ 9308 lines of diff (skipped)
