summaryrefslogtreecommitdiff
path: root/doc/trouble.rst
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2013-09-17 20:15:53 -0400
committerNed Batchelder <ned@nedbatchelder.com>2013-09-17 20:15:53 -0400
commitbcd89039dd7aba5459a1727c44d1661d0a48a96e (patch)
treec394f7d613a1cc03758fe6127a1f4163a637554b /doc/trouble.rst
parentbb098f20ed64bafd3ca14b265f47f657a4be9d79 (diff)
downloadpython-coveragepy-bcd89039dd7aba5459a1727c44d1661d0a48a96e.tar.gz
Remove notes about me being available for custom work, and rewrap many paragraphs.
Diffstat (limited to 'doc/trouble.rst')
-rw-r--r--doc/trouble.rst14
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/trouble.rst b/doc/trouble.rst
index c7693c9..ad82f88 100644
--- a/doc/trouble.rst
+++ b/doc/trouble.rst
@@ -11,9 +11,9 @@ there are some situations it can't cope with. This page details some known
problems, with possible courses of action, and links to coverage.py bug reports
with more information.
-I would love to :ref:`hear from you <contact>` if you have information about any of
-these problems, even just to explain to me why you want them to start working
-properly.
+I would love to :ref:`hear from you <contact>` if you have information about
+any of these problems, even just to explain to me why you want them to start
+working properly.
If your problem isn't discussed here, you can of course search the `coverage.py
bug tracker`_ directly to see if there is some mention of it.
@@ -75,7 +75,8 @@ Really obscure things
---------------------
* Python 2.5 had a bug (`1569356`_) that could make your program behave
- differently when being measured with coverage. This is diagnosed in `issue 51`_.
+ differently when being measured with coverage. This is diagnosed in
+ `issue 51`_.
.. _issue 51: http://bitbucket.org/ned/coveragepy/issue/51/turbogears-15-test-failing-with-coverage
.. _1569356: http://bugs.python.org/issue1569356
@@ -84,5 +85,6 @@ Really obscure things
Still having trouble?
---------------------
-If your problem isn't mentioned here, and isn't already reported in the `coverage.py bug tracker`_,
-please :ref:`get in touch with me <contact>`, we'll figure out a solution.
+If your problem isn't mentioned here, and isn't already reported in the
+`coverage.py bug tracker`_, please :ref:`get in touch with me <contact>`,
+we'll figure out a solution.