summaryrefslogtreecommitdiff
path: root/CHANGES.rst
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2017-05-07 18:20:22 -0400
committerNed Batchelder <ned@nedbatchelder.com>2017-05-07 18:20:22 -0400
commitff089e32d04e517187d1b35e828253cf27da915e (patch)
tree15ae6a5ef01130a5f313dd65b5cd5236293ba24b /CHANGES.rst
parent80cf759b1504fc75e1135cc15a69a827a2439a1f (diff)
downloadpython-coveragepy-git-ff089e32d04e517187d1b35e828253cf27da915e.tar.gz
Use a terser reference to issues
Diffstat (limited to 'CHANGES.rst')
-rw-r--r--CHANGES.rst12
1 files changed, 5 insertions, 7 deletions
diff --git a/CHANGES.rst b/CHANGES.rst
index f3f88f03..6e66c78c 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -15,22 +15,20 @@ Unreleased
Thomas.
- XML reports could produce ``<source>`` and ``<class>`` lines that together
- didn't specify a valid source file path, as described in `issue 526`_. This
- is now fixed.
+ didn't specify a valid source file path. This is now fixed. (`issue 526`_)
-- Namespace packages are no longer warned as having no code, as described in
- `issue 572`_.
+- Namespace packages are no longer warned as having no code. (`issue 572`_)
- Code that uses ``sys.settrace(sys.gettrace())`` in a file that wasn't being
coverage-measured would prevent correct coverage measurement in following
- code. An example of this was running doctests programmatically, as described
- in `issue 575`_. This is now fixed.
+ code. An example of this was running doctests programmatically. This is now
+ fixed. (`issue 575`_)
- Errors printed by the ``coverage`` command now go to stderr instead of
stdout.
- Running ``coverage xml`` in a directory named with non-ASCII characters would
- fail under Python 2, as reported in `issue 573`_. This is now fixed.
+ fail under Python 2. This is now fixed. (`issue 573`_)
.. _issue 526: https://bitbucket.org/ned/coveragepy/issues/526/generated-xml-invalid-paths-for-cobertura
.. _issue 572: https://bitbucket.org/ned/coveragepy/issues/572/no-python-source-warning-for-namespace