From 020562008240d0fd8b00d187a916c8b74040519f Mon Sep 17 00:00:00 2001 From: Ned Batchelder Date: Sun, 7 May 2017 18:20:22 -0400 Subject: Use a terser reference to issues --- CHANGES.rst | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) (limited to 'CHANGES.rst') diff --git a/CHANGES.rst b/CHANGES.rst index f3f88f0..6e66c78 100644 --- a/CHANGES.rst +++ b/CHANGES.rst @@ -15,22 +15,20 @@ Unreleased Thomas. - XML reports could produce ```` and ```` 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 -- cgit v1.2.1