summaryrefslogtreecommitdiff
path: root/CHANGES.rst
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2022-05-18 07:18:51 -0400
committerNed Batchelder <ned@nedbatchelder.com>2022-05-18 07:18:51 -0400
commit803a5494ef23187e920eeb4b42e922b87cda5966 (patch)
tree141923268aef69c8b66324977160f60a7b1e7b24 /CHANGES.rst
parentcde33ba4ded948bfc1fc9c6768db35d7728102c2 (diff)
downloadpython-coveragepy-git-803a5494ef23187e920eeb4b42e922b87cda5966.tar.gz
fix: the SIGTERM handler is now opt-in. #1310
Diffstat (limited to 'CHANGES.rst')
-rw-r--r--CHANGES.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/CHANGES.rst b/CHANGES.rst
index f7258a30..c2772238 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -20,9 +20,16 @@ development at the same time, such as 4.5.x and 5.0.
Unreleased
----------
+- A new setting, :ref:`config_run_sigterm`, controls whether a SIGTERM signal
+ handler is used. In 6.3, the signal handler was always installed, to capture
+ data at unusual process ends. Unfortunately, this introduced other problems
+ (see `issue 1310`_). Now the signal handler is only used if you opt-in by
+ setting ``[run] sigterm = true``.
+
- On Python 3.11, the ``[toml]`` extra no longer installs tomli, instead using
tomllib from the standard library. Thanks `Shantanu <pull 1359_>`_.
+.. _issue 1310: https://github.com/nedbat/coveragepy/issues/1310
.. _pull 1359: https://github.com/nedbat/coveragepy/pull/1359