Ned Batchelder committed afc3c2f

Doc changes for 3.5.2b1

Comments (0)

Files changed (4)

 :history: 20110604T214100, updated for 3.5b1
 :history: 20110629T082200, updated for 3.5
 :history: 20110923T081600, updated for 3.5.1
+:history: 20120429T162100, updated for 3.5.2b1
 These are the major changes for  For a more complete change
 .. _CHANGES.txt:
+Version 3.5.2b1 --- 29 April 2012
+- The HTML report has slightly tweaked controls: the buttons at the top of
+  the page are color-coded to the source lines they affect.
+- Custom CSS can be applied to the HTML report by specifying a CSS file as
+  the extra_css configuration value in the [html] section.
+- Source files with custom encodings declared in a comment at the top are now
+  properly handled during reporting on Python 2.  Python 3 always handled them
+  properly.  This fixes `issue 157`_.
+- Backup files left behind by editors are no longer collected by the source=
+  option, fixing `issue 168`_.
+- If a file doesn't parse properly as Python, we don't report it as an error
+  if the filename seems like maybe it wasn't meant to be Python.  This is a
+  pragmatic fix for `issue 82`_.
+- The ``-m`` switch on ``coverage report``, which includes missing line numbers
+  in the summary report, can now be specifed as ``show_missing`` in the
+  config file.  Closes `issue 173`_.
+- When running a module with ``coverage run -m <modulename>``, certain details
+  of the execution environment weren't the same as for
+  ``python -m <modulename>``.  This had the unfortunate side-effect of making
+  ``coverage run -m unittest discover`` not work if you had tests in a
+  directory named "test".  This fixes `issue 155`_.
+- Now the exit status of your product code is properly used as the process
+  status when running ``python -m coverage run ...``.  Thanks, JT Olds.
+- When installing into pypy, we no longer attempt (and fail) to compile
+  the C tracer function, closing `issue 166`_.
+.. _issue 82:
+.. _issue 155:
+.. _issue 157:
+.. _issue 166:
+.. _issue 168:
+.. _issue 173:
 Version 3.5.1 --- 23 September 2011
 # General information about the project.
 project = u''
-copyright = u'2009-2011, Ned Batchelder'
+copyright = u'2009-2012, Ned Batchelder'
 # The version info for the project you're documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the
 # built documents.
 # The short X.Y version.
-version = '3.5.1'
+version = '3.5.2'
 # The full version, including alpha/beta/rc tags.
-release = '3.5.1'
+release = '3.5.2b1'
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
 :history: 20110629T082300, update for 3.5
 :history: 20110827T221800, update for 3.5.1b1
 :history: 20110923T081800, update for 3.5.1
+:history: 20120429T162100, updated for 3.5.2b1 is a tool for measuring code coverage of Python programs. It
 .. ifconfig:: prerelease
-    The latest version is 3.5.1b1, released 28 August 2011.
+    The latest version is 3.5.2b1, released 29 April 2012.
     *This is a pre-release build.  The usual warnings about possible bugs apply.*
     It is supported on Python versions 2.3 through 3.2.
-    The latest stable version is 3.5, `described here`_.
+    The latest stable version is 3.5.1, `described here`_.
 .. _described here:
 :history: 20110604T213400, updated for 3.5b1.
 :history: 20110629T082400, updated for 3.5.
 :history: 20110923T081900, updated for 3.5.1.
+:history: 20120429T162500, updated for 3.5.2b1
 .. highlight:: console
 coverage installed properly::
     $ coverage --version
-, version 3.5.1.
+, version 3.5.2b1.