Sourced from coverage's changelog.
Version 7.6.8 — 2024-11-23
Fix: the LCOV report code assumed that a branch line that took no branches meant that the entire line was unexecuted. This isn't true in a few cases: the line might always raise an exception, or might have been optimized away. Fixes
issue 1896
_.Fix: similarly, the HTML report will now explain that a line that jumps to none of its expected destinations must have always raised an exception. Previously, it would say something nonsensical like, "line 4 didn't jump to line 5 because line 4 was never true, and it didn't jump to line 7 because line 4 was always true." This was also shown in
issue 1896
_... _issue 1896: nedbat/coveragepy#1896
.. _changes_7-6-7:
6134266
docs: sample HTML for 7.6.8041f963
docs: prep for 7.6.87fe48b6
build: don't search generated report filesf219144
docs: start changelog entries with capital lettersd1a916a
fix: a line that branches nowhere must always raise an exception2ace7a2
fix: don't assume 'no branches' means 'not executed' #18963ed5915
style: all of ci should use underscores0db86f2
build: automate updating readthedocs2a89551
chore: make upgrade (not sure why files became absolute)ba9c157
chore: make doc_upgrade