diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2013-09-17 20:15:53 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2013-09-17 20:15:53 -0400 |
| commit | a73c2b9bfe6679423cc8e1e8f83538a1caa030b4 (patch) | |
| tree | f8df74c332d4b3c068bd493c5a4c1a3f5561b65c /doc/trouble.rst | |
| parent | a5d67a849961b4d16ef72f08e3ebb7ddf7d96de8 (diff) | |
| download | python-coveragepy-git-a73c2b9bfe6679423cc8e1e8f83538a1caa030b4.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.rst | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/trouble.rst b/doc/trouble.rst index c7693c9e..ad82f880 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. |