./devel/py-coverage, Python module that measures code coverage for Python

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 4.4.1, Package name: py27-coverage-4.4.1, Maintainer: kamel.derouiche

Python module that measures code coverage during Python execution.
It uses the code analysis tools and tracing hooks provided in
the Python standard library to determine which lines are executable,
and which have been executed.


Required to run:
[devel/py-setuptools] [lang/python27]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: 4f7ed244125c3fc174bca3d3857b6f92b9f652bf
RMD160: 6254b6672632af2f3c5b5241df4b97d4245a501b
Filesize: 361.122 KB

Version history: (Expand)


CVS history: (Expand)


   2017-05-17 13:39:58 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
Version 4.4.1
- No code changes: just corrected packaging for Python 2.7 Linux wheels.

Version 4.4
- Reports could produce the wrong file names for packages, reporting ``pkg.py``
  instead of the correct ``pkg/__init__.py``.  This is now fixed.  Thanks, Dirk
  Thomas.

- XML reports could produce ``<source>`` and ``<class>`` lines that \ 
together
  didn't specify a valid source file path.  This is now fixed. (`issue 526`_)

- 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. 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. This is now fixed. (`issue 573`_)
   2016-08-28 17:48:37 by Thomas Klausner | Files touched by this commit (112)
Log message:
Remove unnecessary PLIST_SUBST and FILES_SUBST that are now provided
by the infrastructure.

Mark a couple more packages as not ready for python-3.x.
   2016-06-08 19:43:49 by Thomas Klausner | Files touched by this commit (356)
Log message:
Switch to MASTER_SITES_PYPI.
   2015-11-07 22:43:21 by Thomas Klausner | Files touched by this commit (1)
Log message:
Add some more test dependencies, and run the correct tool for testing.

Still more changes needed to get this anywhere approximatelysuccessful.
   2015-11-07 20:12:09 by Thomas Klausner | Files touched by this commit (3) | Package updated
Log message:
Update py-coverage to 4.0.2:

Version 4.0.2 --- 4 November 2015
---------------------------------

- More work on supporting unusually encoded source. Fixed `issue 431`_.

- Files or directories with non-ASCII characters are now handled properly,
  fixing `issue 432`_.

- Setting a trace function with sys.settrace was broken by a change in 4.0.1,
  as reported in `issue 436`_.  This is now fixed.

- Officially support PyPy 4.0, which required no changes, just updates to the
  docs.

.. _issue 431: \ 
https://bitbucket.org/ned/coveragepy/is … ith-cp1252
.. _issue 432: \ 
https://bitbucket.org/ned/coveragepy/is … rs-various
.. _issue 436: \ 
https://bitbucket.org/ned/coveragepy/is … -rise-from

Version 4.0.1 --- 13 October 2015
---------------------------------

- When combining data files, unreadable files will now generate a warning
  instead of failing the command.  This is more in line with the older
  coverage.py v3.7.1 behavior, which silently ignored unreadable files.
  Prompted by `issue 418`_.

- The --skip-covered option would skip reporting on 100% covered files, but
  also skipped them when calculating total coverage.  This was wrong, it should
  only remove lines from the report, not change the final answer.  This is now
  fixed, closing `issue 423`_.

- In 4.0, the data file recorded a summary of the system on which it was run.
  Combined data files would keep all of those summaries.  This could lead to
  enormous data files consisting of mostly repetitive useless information. That
  summary is now gone, fixing `issue 415`_.  If you want summary information,
  get in touch, and we'll figure out a better way to do it.

- Test suites that mocked os.path.exists would experience strange failures, due
  to coverage.py using their mock inadvertently.  This is now fixed, closing
  `issue 416`_.

- Importing a ``__init__`` module explicitly would lead to an error:
  ``AttributeError: 'module' object has no attribute '__path__'``, as reported
  in `issue 410`_.  This is now fixed.

- Code that uses ``sys.settrace(sys.gettrace())`` used to incur a more than 2x
  speed penalty.  Now there's no penalty at all. Fixes `issue 397`_.

- Pyexpat C code will no longer be recorded as a source file, fixing
  `issue 419`_.

- The source kit now contains all of the files needed to have a complete source
  tree, re-fixing `issue 137`_ and closing `issue 281`_.

.. _issue 281: \ 
https://bitbucket.org/ned/coveragepy/is … ing-in-the
.. _issue 397: \ 
https://bitbucket.org/ned/coveragepy/is … erage-with
.. _issue 410: \ 
https://bitbucket.org/ned/coveragepy/is … ect-has-no
.. _issue 415: \ 
https://bitbucket.org/ned/coveragepy/is … ates-cause
.. _issue 416: \ 
https://bitbucket.org/ned/coveragepy/is … s-failures
.. _issue 418: https://bitbucket.org/ned/coveragepy/is … arse-error
.. _issue 419: \ 
https://bitbucket.org/ned/coveragepy/is … -path-to-c
.. _issue 423: \ 
https://bitbucket.org/ned/coveragepy/is … rted-total

Version 4.0 --- 20 September 2015
---------------------------------

No changes from 4.0b3

Version 4.0b3 --- 7 September 2015
----------------------------------

- Reporting on an unmeasured file would fail with a traceback.  This is now
  fixed, closing `issue 403`_.

- The Jenkins ShiningPanda plugin looks for an obsolete file name to find the
  HTML reports to publish, so it was failing under coverage.py 4.0.  Now we
  create that file if we are running under Jenkins, to keep things working
  smoothly. `issue 404`_.

- Kits used to include tests and docs, but didn't install them anywhere, or
  provide all of the supporting tools to make them useful.  Kits no longer
  include tests and docs.  If you were using them from the older packages, get
  in touch and help me understand how.

.. _issue 403: \ 
https://bitbucket.org/ned/coveragepy/is … r-nonetype
.. _issue 404: \ 
https://bitbucket.org/ned/coveragepy/is … -find-html

Version 4.0b2 --- 22 August 2015
--------------------------------

- 4.0b1 broke --append creating new data files.  This is now fixed, closing
  `issue 392`_.

- ``py.test --cov`` can write empty data, then touch files due to ``--source``,
  which made coverage.py mistakenly force the data file to record lines instead
  of arcs.  This would lead to a "Can't combine line data with arc \ 
data" error
  message.  This is now fixed, and changed some method names in the
  CoverageData interface.  Fixes `issue 399`_.

- `CoverageData.read_fileobj` and `CoverageData.write_fileobj` replace the
  `.read` and `.write` methods, and are now properly inverses of each other.

- When using ``report --skip-covered``, a message will now be included in the
  report output indicating how many files were skipped, and if all files are
  skipped, coverage.py won't accidentally scold you for having no data to
  report.  Thanks, Krystian Kichewko.

- A new conversion utility has been added:  ``python -m coverage.pickle2json``
  will convert v3.x pickle data files to v4.x JSON data files.  Thanks,
  Alexander Todorov.  Closes `issue 395`_.

- A new version identifier is available, `coverage.version_info`, a plain tuple
  of values similar to `sys.version_info`_.

.. _issue 392: \ 
https://bitbucket.org/ned/coveragepy/is … erage-file
.. _issue 395: \ 
https://bitbucket.org/ned/coveragepy/is … s-well-for
.. _issue 399: \ 
https://bitbucket.org/ned/coveragepy/is … -line-data
.. _sys.version_info: https://docs.python.org/3/library/sys.h … rsion_info

Version 4.0b1 --- 2 August 2015
-------------------------------

- Coverage.py is now licensed under the Apache 2.0 license.  See NOTICE.txt for
  details.  Closes `issue 313`_.

- The data storage has been completely revamped.  The data file is now
  JSON-based instead of a pickle, closing `issue 236`_.  The `CoverageData`
  class is now a public supported documented API to the data file.

- A new configuration option, ``[run] note``, lets you set a note that will be
  stored in the `runs` section of the data file.  You can use this to annotate
  the data file with any information you like.

- Unrecognized configuration options will now print an error message and stop
  coverage.py.  This should help prevent configuration mistakes from passing
  silently.  Finishes `issue 386`_.

- In parallel mode, ``coverage erase`` will now delete all of the data files,
  fixing `issue 262`_.

- Coverage.py now accepts a directory name for ``coverage run`` and will run a
  ``__main__.py`` found there, just like Python will.  Fixes `issue 252`_.
  Thanks, Dmitry Trofimov.

- The XML report now includes a ``missing-branches`` attribute.  Thanks, Steve
  Peak.  This is not a part of the Cobertura DTD, so the XML report no longer
  references the DTD.

- Missing branches in the HTML report now have a bit more information in the
  right-hand annotations.  Hopefully this will make their meaning clearer.

- All the reporting functions now behave the same if no data had been
  collected, exiting with a status code of 1.  Fixed ``fail_under`` to be
  applied even when the report is empty.  Thanks, Ionel Cristian Mărieș.

- Plugins are now initialized differently.  Instead of looking for a class
  called ``Plugin``, coverage.py looks for a function called ``coverage_init``.

- A file-tracing plugin can now ask to have built-in Python reporting by
  returning `"python"` from its `file_reporter()` method.

- Code that was executed with `exec` would be mis-attributed to the file that
  called it.  This is now fixed, closing `issue 380`_.

- The ability to use item access on `Coverage.config` (introduced in 4.0a2) has
  been changed to a more explicit `Coverage.get_option` and
  `Coverage.set_option` API.

- The ``Coverage.use_cache`` method is no longer supported.

- The private method ``Coverage._harvest_data`` is now called
  ``Coverage.get_data``, and returns the ``CoverageData`` containing the
  collected data.

- The project is consistently referred to as "coverage.py" throughout \ 
the code
  and the documentation, closing `issue 275`_.

- Combining data files with an explicit configuration file was broken in 4.0a6,
  but now works again, closing `issue 385`_.

- ``coverage combine`` now accepts files as well as directories.

- The speed is back to 3.7.1 levels, after having slowed down due to plugin
  support, finishing up `issue 387`_.

.. _issue 236: \ 
https://bitbucket.org/ned/coveragepy/is … d-feel-bad
.. _issue 252: \ 
https://bitbucket.org/ned/coveragepy/is … ogram-with
.. _issue 262: \ 
https://bitbucket.org/ned/coveragepy/is … -erase-all
.. _issue 275: \ 
https://bitbucket.org/ned/coveragepy/is … s-coverage
.. _issue 313: \ 
https://bitbucket.org/ned/coveragepy/is … g-2-3-or-4
.. _issue 380: \ 
https://bitbucket.org/ned/coveragepy/is … luded-from
.. _issue 385: \ 
https://bitbucket.org/ned/coveragepy/is … ith-rcfile
.. _issue 386: \ 
https://bitbucket.org/ned/coveragepy/is … figuration
.. _issue 387: \ 
https://bitbucket.org/ned/coveragepy/is … -371-to-40

.. 40 issues closed in 4.0 below here

Version 4.0a6 --- 21 June 2015
------------------------------

- Python 3.5b2 and PyPy 2.6.0 are supported.

- The original module-level function interface to coverage.py is no longer
  supported.  You must now create a ``coverage.Coverage`` object, and use
  methods on it.

- The ``coverage combine`` command now accepts any number of directories as
  arguments, and will combine all the data files from those directories.  This
  means you don't have to copy the files to one directory before combining.
  Thanks, Christine Lytwynec.  Finishes `issue 354`_.

- Branch coverage couldn't properly handle certain extremely long files. This
  is now fixed (`issue 359`_).

- Branch coverage didn't understand yield statements properly.  Mickie Betz
  persisted in pursuing this despite Ned's pessimism.  Fixes `issue 308`_ and
  `issue 324`_.

- The COVERAGE_DEBUG environment variable can be used to set the ``[run] debug``
  configuration option to control what internal operations are logged.

- HTML reports were truncated at formfeed characters.  This is now fixed
  (`issue 360`_).  It's always fun when the problem is due to a `bug in the
  Python standard library <http://bugs.python.org/issue19035>`_.

- Files with incorrect encoding declaration comments are no longer ignored by
  the reporting commands, fixing `issue 351`_.

- HTML reports now include a timestamp in the footer, closing `issue 299`_.
  Thanks, Conrad Ho.

- HTML reports now begrudgingly use double-quotes rather than single quotes,
  because there are "software engineers" out there writing tools that \ 
read HTML
  and somehow have no idea that single quotes exist.  Capitulates to the absurd
  `issue 361`_.  Thanks, Jon Chappell.

- The ``coverage annotate`` command now handles non-ASCII characters properly,
  closing `issue 363`_.  Thanks, Leonardo Pistone.

- Drive letters on Windows were not normalized correctly, now they are. Thanks,
  Ionel Cristian Mărieș.

- Plugin support had some bugs fixed, closing `issue 374`_ and `issue 375`_.
  Thanks, Stefan Behnel.

.. _issue 299: \ 
https://bitbucket.org/ned/coveragepy/is … d-hh-mm-in
.. _issue 308: \ 
https://bitbucket.org/ned/coveragepy/is … h-coverage
.. _issue 324: \ 
https://bitbucket.org/ned/coveragepy/is … h-coverage
.. _issue 351: \ 
https://bitbucket.org/ned/coveragepy/is … re-ignored
.. _issue 354: \ 
https://bitbucket.org/ned/coveragepy/is … -a-list-of
.. _issue 359: https://bitbucket.org/ned/coveragepy/is … hunk-error
.. _issue 360: \ 
https://bitbucket.org/ned/coveragepy/is … n-the-code
.. _issue 361: \ 
https://bitbucket.org/ned/coveragepy/is … -output-to
.. _issue 363: \ 
https://bitbucket.org/ned/coveragepy/is … -happy-fun
.. _issue 374: \ 
https://bitbucket.org/ned/coveragepy/is … ps-fail-in
.. _issue 375: \ 
https://bitbucket.org/ned/coveragepy/is … -byte-code

Version 4.0a5 --- 16 February 2015
----------------------------------

- Plugin support is now implemented in the C tracer instead of the Python
  tracer. This greatly improves the speed of tracing projects using plugins.

- Coverage.py now always adds the current directory to sys.path, so that
  plugins can import files in the current directory (`issue 358`_).

- If the `config_file` argument to the Coverage constructor is specified as
  ".coveragerc", it is treated as if it were True.  This means setup.cfg is
  also examined, and a missing file is not considered an error (`issue 357`_).

- Wildly experimental: support for measuring processes started by the
  multiprocessing module.  To use, set ``--concurrency=multiprocessing``,
  either on the command line or in the .coveragerc file (`issue 117`_). Thanks,
  Eduardo Schettino.  Currently, this does not work on Windows.

- A new warning is possible, if a desired file isn't measured because it was
  imported before coverage.py was started (`issue 353`_).

- The `coverage.process_startup` function now will start coverage measurement
  only once, no matter how many times it is called.  This fixes problems due
  to unusual virtualenv configurations (`issue 340`_).

- Added 3.5.0a1 to the list of supported CPython versions.

.. _issue 117: \ 
https://bitbucket.org/ned/coveragepy/is … ode-run-by
.. _issue 340: https://bitbucket.org/ned/coveragepy/is … rror-subpy
.. _issue 353: \ 
https://bitbucket.org/ned/coveragepy/is … third-case
.. _issue 357: \ 
https://bitbucket.org/ned/coveragepy/is … eragerc-is
.. _issue 358: \ 
https://bitbucket.org/ned/coveragepy/is … uld-adjust

Version 4.0a4 --- 25 January 2015
---------------------------------

- Plugins can now provide sys_info for debugging output.

- Started plugins documentation.

- Prepared to move the docs to readthedocs.org.

Version 4.0a3 --- 20 January 2015
---------------------------------

- Reports now use file names with extensions.  Previously, a report would
  describe a/b/c.py as "a/b/c".  Now it is shown as \ 
"a/b/c.py".  This allows
  for better support of non-Python files, and also fixed `issue 69`_.

- The XML report now reports each directory as a package again.  This was a bad
  regression, I apologize.  This was reported in `issue 235`_, which is now
  fixed.

- A new configuration option for the XML report: ``[xml] package_depth``
  controls which directories are identified as packages in the report.
  Directories deeper than this depth are not reported as packages.
  The default is that all directories are reported as packages.
  Thanks, Lex Berezhny.

- When looking for the source for a frame, check if the file exists. On
  Windows, .pyw files are no longer recorded as .py files. Along the way, this
  fixed `issue 290`_.

- Empty files are now reported as 100% covered in the XML report, not 0%
  covered (`issue 345`_).

- Regexes in the configuration file are now compiled as soon as they are read,
  to provide error messages earlier (`issue 349`_).

.. _issue 69: \ 
https://bitbucket.org/ned/coveragepy/is … hat-doesnt
.. _issue 235: \ 
https://bitbucket.org/ned/coveragepy/is … xml-report
.. _issue 290: \ 
https://bitbucket.org/ned/coveragepy/is … -pyw-files
.. _issue 345: \ 
https://bitbucket.org/ned/coveragepy/is … mpty-files
.. _issue 349: \ 
https://bitbucket.org/ned/coveragepy/is … an-earlier

Version 4.0a2 --- 14 January 2015
---------------------------------

- Officially support PyPy 2.4, and PyPy3 2.4.  Drop support for
  CPython 3.2 and older versions of PyPy.  The code won't work on CPython 3.2.
  It will probably still work on older versions of PyPy, but I'm not testing
  against them.

- Plugins!

- The original command line switches (`-x` to run a program, etc) are no
  longer supported.

- A new option: `coverage report --skip-covered` will reduce the number of
  files reported by skipping files with 100% coverage.  Thanks, Krystian
  Kichewko.  This means that empty `__init__.py` files will be skipped, since
  they are 100% covered, closing `issue 315`_.

- You can now specify the ``--fail-under`` option in the ``.coveragerc`` file
  as the ``[report] fail_under`` option.  This closes `issue 314`_.

- The ``COVERAGE_OPTIONS`` environment variable is no longer supported.  It was
  a hack for ``--timid`` before configuration files were available.

- The HTML report now has filtering.  Type text into the Filter box on the
  index page, and only modules with that text in the name will be shown.
  Thanks, Danny Allen.

- The textual report and the HTML report used to report partial branches
  differently for no good reason.  Now the text report's "missing branches"
  column is a "partial branches" column so that both reports show the same
  numbers.  This closes `issue 342`_.

- If you specify a ``--rcfile`` that cannot be read, you will get an error
  message.  Fixes `issue 343`_.

- The ``--debug`` switch can now be used on any command.

- You can now programmatically adjust the configuration of coverage.py by
  setting items on `Coverage.config` after construction.

- A module run with ``-m`` can be used as the argument to ``--source``, fixing
  `issue 328`_.  Thanks, Buck Evan.

- The regex for matching exclusion pragmas has been fixed to allow more kinds
  of whitespace, fixing `issue 334`_.

- Made some PyPy-specific tweaks to improve speed under PyPy.  Thanks, Alex
  Gaynor.

- In some cases, with a source file missing a final newline, coverage.py would
  count statements incorrectly.  This is now fixed, closing `issue 293`_.

- The status.dat file that HTML reports use to avoid re-creating files that
  haven't changed is now a JSON file instead of a pickle file.  This obviates
  `issue 287`_ and `issue 237`_.

.. _issue 237: \ 
https://bitbucket.org/ned/coveragepy/is … -statusdat
.. _issue 287: \ 
https://bitbucket.org/ned/coveragepy/is … e-protocol
.. _issue 293: \ 
https://bitbucket.org/ned/coveragepy/is … rong-if-no
.. _issue 314: \ 
https://bitbucket.org/ned/coveragepy/is … coveragerc
.. _issue 315: \ 
https://bitbucket.org/ned/coveragepy/is … __init__py
.. _issue 328: \ 
https://bitbucket.org/ned/coveragepy/is … run-source
.. _issue 334: \ 
https://bitbucket.org/ned/coveragepy/is … -character
.. _issue 342: \ 
https://bitbucket.org/ned/coveragepy/is … rts-differ
.. _issue 343: \ 
https://bitbucket.org/ned/coveragepy/is … ent-config

Version 4.0a1 --- 27 September 2014
-----------------------------------

- Python versions supported are now CPython 2.6, 2.7, 3.2, 3.3, and 3.4, and
  PyPy 2.2.

- Gevent, eventlet, and greenlet are now supported, closing `issue 149`_.
  The ``concurrency`` setting specifies the concurrency library in use.  Huge
  thanks to Peter Portante for initial implementation, and to Joe Jevnik for
  the final insight that completed the work.

- Options are now also read from a setup.cfg file, if any.  Sections are
  prefixed with "coverage:", so the ``[run]`` options will be read from the
  ``[coverage:run]`` section of setup.cfg.  Finishes `issue 304`_.

- The ``report -m`` command can now show missing branches when reporting on
  branch coverage.  Thanks, Steve Leonard. Closes `issue 230`_.

- The XML report now contains a <source> element, fixing `issue 94`_.  Thanks
  Stan Hu.

- The class defined in the coverage module is now called ``Coverage`` instead
  of ``coverage``, though the old name still works, for backward compatibility.

- The ``fail-under`` value is now rounded the same as reported results,
  preventing paradoxical results, fixing `issue 284`_.

- The XML report will now create the output directory if need be, fixing
  `issue 285`_.  Thanks, Chris Rose.

- HTML reports no longer raise UnicodeDecodeError if a Python file has
  undecodable characters, fixing `issue 303`_ and `issue 331`_.

- The annotate command will now annotate all files, not just ones relative to
  the current directory, fixing `issue 57`_.

- The coverage module no longer causes deprecation warnings on Python 3.4 by
  importing the imp module, fixing `issue 305`_.

- Encoding declarations in source files are only considered if they are truly
  comments.  Thanks, Anthony Sottile.

.. _issue 57: \ 
https://bitbucket.org/ned/coveragepy/is … otate-many
.. _issue 94: \ 
https://bitbucket.org/ned/coveragepy/is … ce-sources
.. _issue 149: \ 
https://bitbucket.org/ned/coveragepy/is … oks-broken
.. _issue 230: \ 
https://bitbucket.org/ned/coveragepy/is … ranches-in
.. _issue 284: \ 
https://bitbucket.org/ned/coveragepy/is … -precision
.. _issue 285: \ 
https://bitbucket.org/ned/coveragepy/is … -directory
.. _issue 303: https://bitbucket.org/ned/coveragepy/is … ecodeerror
.. _issue 304: \ 
https://bitbucket.org/ned/coveragepy/is … m-setupcfg
.. _issue 305: \ 
https://bitbucket.org/ned/coveragepy/is … imp-module
.. _issue 331: \ 
https://bitbucket.org/ned/coveragepy/is … on-python2
   2015-11-03 04:29:40 by Alistair G. Crooks | Files touched by this commit (1995)
Log message:
Add SHA512 digests for distfiles for devel category

Issues found with existing distfiles:
	distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
	distfiles/fortran-utils-1.1.tar.gz
	distfiles/ivykis-0.39.tar.gz
	distfiles/enum-1.11.tar.gz
	distfiles/pvs-3.2-libraries.tgz
	distfiles/pvs-3.2-linux.tgz
	distfiles/pvs-3.2-solaris.tgz
	distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
   2014-01-27 21:46:23 by Thomas Klausner | Files touched by this commit (1)
Log message:
Simplify PLIST and fix it for python-2.6.
   2014-01-26 01:52:05 by Thomas Klausner | Files touched by this commit (4) | Package updated
Log message:
Update to 3.7.1:

3.7.1 -- 13 December 2013
-------------------------

- Improved the speed of HTML report generation by about 20%.

- Fixed the mechanism for finding OS-installed static files for the HTML report
  so that it will actually find OS-installed static files.

3.7 --- 6 October 2013
----------------------

- Added the ``--debug`` switch to ``coverage run``.  It accepts a list of
  options indicating the type of internal activity to log to stderr.

- Improved the branch coverage facility, fixing `issue 92`_ and `issue 175`_.

- Running code with ``coverage run -m`` now behaves more like Python does,
  setting sys.path properly, which fixes `issue 207`_ and `issue 242`_.

- Coverage can now run .pyc files directly, closing `issue 264`_.

- Coverage properly supports .pyw files, fixing `issue 261`_.

- Omitting files within a tree specified with the ``source`` option would
  cause them to be incorrectly marked as unexecuted, as described in
  `issue 218`_.  This is now fixed.

- When specifying paths to alias together during data combining, you can now
  specify relative paths, fixing `issue 267`_.

- Most file paths can now be specified with username expansion (``~/src``, or
  ``~build/src``, for example), and with environment variable expansion
  (``build/$BUILDNUM/src``).

- Trying to create an XML report with no files to report on, would cause a
  ZeroDivideError, but no longer does, fixing `issue 250`_.

- When running a threaded program under the Python tracer, coverage no longer
  issues a spurious warning about the trace function changing: "Trace function
  changed, measurement is likely wrong: None."  This fixes `issue 164`_.

- Static files necessary for HTML reports are found in system-installed places,
  to ease OS-level packaging of coverage.py.  Closes `issue 259`_.

- Source files with encoding declarations, but a blank first line, were not
  decoded properly.  Now they are.  Thanks, Roger Hu.

- The source kit now includes the ``__main__.py`` file in the root coverage
  directory, fixing `issue 255`_.

.. _issue 92: \ 
https://bitbucket.org/ned/coveragepy/is … roperly-in
.. _issue 164: \ 
https://bitbucket.org/ned/coveragepy/is … when-using
.. _issue 175: \ 
https://bitbucket.org/ned/coveragepy/is … in-certain
.. _issue 207: \ 
https://bitbucket.org/ned/coveragepy/is … package-in
.. _issue 242: \ 
https://bitbucket.org/ned/coveragepy/is … oesnt-work
.. _issue 218: \ 
https://bitbucket.org/ned/coveragepy/is … -omit-flag
.. _issue 250: \ 
https://bitbucket.org/ned/coveragepy/is … generating
.. _issue 255: \ 
https://bitbucket.org/ned/coveragepy/is … ncluded-in
.. _issue 259: \ 
https://bitbucket.org/ned/coveragepy/is … hird-party
.. _issue 261: \ 
https://bitbucket.org/ned/coveragepy/is … d-properly
.. _issue 264: \ 
https://bitbucket.org/ned/coveragepy/is … -pyc-files
.. _issue 267: \ 
https://bitbucket.org/ned/coveragepy/is … -dont-work

Version 3.6 --- 5 January 2013
------------------------------

- Added a page to the docs about troublesome situations, closing `issue 226`_,
  and added some info to the TODO file, closing `issue 227`_.

.. _issue 226: \ 
https://bitbucket.org/ned/coveragepy/is … cribe-when
.. _issue 227: https://bitbucket.org/ned/coveragepy/is … pdate-todo

Version 3.6b3 --- 29 December 2012
----------------------------------

- Beta 2 broke the nose plugin. It's fixed again, closing `issue 224`_.

.. _issue 224: https://bitbucket.org/ned/coveragepy/is … nosexcover

Version 3.6b2 --- 23 December 2012
----------------------------------

- Coverage.py runs on Python 2.3 and 2.4 again. It was broken in 3.6b1.

- The C extension is optionally compiled using a different more widely-used
  technique, taking another stab at fixing `issue 80`_ once and for all.

- Combining data files would create entries for phantom files if used with
  ``source`` and path aliases.  It no longer does.

- ``debug sys`` now shows the configuration file path that was read.

- If an oddly-behaved package claims that code came from an empty-string
  filename, coverage.py no longer associates it with the directory name,
  fixing `issue 221`_.

.. _issue 80: \ 
https://bitbucket.org/ned/coveragepy/is … ow-we-cant
.. _issue 221: \ 
https://bitbucket.org/ned/coveragepy/is … h-pyratemp

Version 3.6b1 --- 28 November 2012
----------------------------------

- Wildcards in ``include=`` and ``omit=`` arguments were not handled properly
  in reporting functions, though they were when running.  Now they are handled
  uniformly, closing `issue 143`_ and `issue 163`_.  **NOTE**: it is possible
  that your configurations may now be incorrect.  If you use ``include`` or
  ``omit`` during reporting, whether on the command line, through the API, or
  in a configuration file, please check carefully that you were not relying on
  the old broken behavior.

- The **report**, **html**, and **xml** commands now accept a ``--fail-under``
  switch that indicates in the exit status whether the coverage percentage was
  less than a particular value.  Closes `issue 139`_.

- The reporting functions coverage.report(), coverage.html_report(), and
  coverage.xml_report() now all return a float, the total percentage covered
  measurement.

- The HTML report's title can now be set in the configuration file, with the
  ``--title`` switch on the command line, or via the API.

- Configuration files now support substitution of environment variables, using
  syntax like ``${WORD}``.  Closes `issue 97`_.

- Embarrassingly, the `[xml] output=` setting in the .coveragerc file simply
  didn't work.  Now it does.

- The XML report now consistently uses filenames for the filename attribute,
  rather than sometimes using module names.  Fixes `issue 67`_.
  Thanks, Marcus Cobden.

- Coverage percentage metrics are now computed slightly differently under
  branch coverage.  This means that completely unexecuted files will now
  correctly have 0% coverage, fixing `issue 156`_.  This also means that your
  total coverage numbers will generally now be lower if you are measuring
  branch coverage.

- When installing, now in addition to creating a "coverage" command, \ 
two new
  aliases are also installed.  A "coverage2" or "coverage3" \ 
command will be
  created, depending on whether you are installing in Python 2.x or 3.x.
  A "coverage-X.Y" command will also be created corresponding to your \ 
specific
  version of Python.  Closes `issue 111`_.

- The coverage.py installer no longer tries to bootstrap setuptools or
  Distribute.  You must have one of them installed first, as `issue 202`_
  recommended.

- The coverage.py kit now includes docs (closing `issue 137`_) and tests.

- On Windows, files are now reported in their correct case, fixing `issue 89`_
  and `issue 203`_.

- If a file is missing during reporting, the path shown in the error message
  is now correct, rather than an incorrect path in the current directory.
  Fixes `issue 60`_.

- Running an HTML report in Python 3 in the same directory as an old Python 2
  HTML report would fail with a UnicodeDecodeError. This issue (`issue 193`_)
  is now fixed.

- Fixed yet another error trying to parse non-Python files as Python, this
  time an IndentationError, closing `issue 82`_ for the fourth time...

- If `coverage xml` fails because there is no data to report, it used to
  create a zero-length XML file.  Now it doesn't, fixing `issue 210`_.

- Jython files now work with the ``--source`` option, fixing `issue 100`_.

- Running coverage under a debugger is unlikely to work, but it shouldn't fail
  with "TypeError: 'NoneType' object is not iterable".  Fixes `issue 201`_.

- On some Linux distributions, when installed with the OS package manager,
  coverage.py would report its own code as part of the results.  Now it won't,
  fixing `issue 214`_, though this will take some time to be repackaged by the
  operating systems.

- Docstrings for the legacy singleton methods are more helpful.  Thanks Marius
  Gedminas.  Closes `issue 205`_.

- The pydoc tool can now show docmentation for the class `coverage.coverage`.
  Closes `issue 206`_.

- Added a page to the docs about contributing to coverage.py, closing
  `issue 171`_.

- When coverage.py ended unsuccessfully, it may have reported odd errors like
  ``'NoneType' object has no attribute 'isabs'``.  It no longer does,
  so kiss `issue 153`_ goodbye.

.. _issue 60: \ 
https://bitbucket.org/ned/coveragepy/is … -pyc-files
.. _issue 67: \ 
https://bitbucket.org/ned/coveragepy/is … -generated
.. _issue 82: \ 
https://bitbucket.org/ned/coveragepy/is … tml-report
.. _issue 89: \ 
https://bitbucket.org/ned/coveragepy/is … eported-in
.. _issue 97: \ 
https://bitbucket.org/ned/coveragepy/is … bles-to-be
.. _issue 100: \ 
https://bitbucket.org/ned/coveragepy/is … r-packages
.. _issue 111: \ 
https://bitbucket.org/ned/coveragepy/is … th-pip-not
.. _issue 137: \ 
https://bitbucket.org/ned/coveragepy/is … stribution
.. _issue 139: \ 
https://bitbucket.org/ned/coveragepy/is … e-in-tests
.. _issue 143: \ 
https://bitbucket.org/ned/coveragepy/is … n-coverage
.. _issue 153: \ 
https://bitbucket.org/ned/coveragepy/is … e-triggers
.. _issue 156: \ 
https://bitbucket.org/ned/coveragepy/is … e-shows-14
.. _issue 163: \ 
https://bitbucket.org/ned/coveragepy/is … t-filename
.. _issue 171: \ 
https://bitbucket.org/ned/coveragepy/is … -run-tests
.. _issue 193: \ 
https://bitbucket.org/ned/coveragepy/is … -on-htmlpy
.. _issue 201: \ 
https://bitbucket.org/ned/coveragepy/is … th-pydb-on
.. _issue 202: \ 
https://bitbucket.org/ned/coveragepy/is … etuppy-and
.. _issue 203: \ 
https://bitbucket.org/ned/coveragepy/is … n-filename
.. _issue 205: \ 
https://bitbucket.org/ned/coveragepy/is … e-friendly
.. _issue 206: \ 
https://bitbucket.org/ned/coveragepy/is … h-an-error
.. _issue 210: \ 
https://bitbucket.org/ned/coveragepy/is … verage-xml
.. _issue 214: \ 
https://bitbucket.org/ned/coveragepy/is … on-precise

Version 3.5.3 --- 29 September 2012
-----------------------------------

- Line numbers in the HTML report line up better with the source lines, fixing
  `issue 197`_, thanks Marius Gedminas.

- When specifying a directory as the source= option, the directory itself no
  longer needs to have a ``__init__.py`` file, though its subdirectories do, to
  be considered as source files.

- Files encoded as UTF-8 with a BOM are now properly handled, fixing
  `issue 179`_.  Thanks, Pablo Carballo.

- Fixed more cases of non-Python files being reported as Python source, and
  then not being able to parse them as Python.  Closes `issue 82`_ (again).
  Thanks, Julian Berman.

- Fixed memory leaks under Python 3, thanks, Brett Cannon. Closes `issue 147`_.

- Optimized .pyo files may not have been handled correctly, `issue 195`_.
  Thanks, Marius Gedminas.

- Certain unusually named file paths could have been mangled during reporting,
  `issue 194`_.  Thanks, Marius Gedminas.

- Try to do a better job of the impossible task of detecting when we can't
  build the C extension, fixing `issue 183`_.

- Testing is now done with `tox`_, thanks, Marc Abramowitz.

.. _issue 82: \ 
https://bitbucket.org/ned/coveragepy/is … tml-report
.. _issue 147: \ 
https://bitbucket.org/ned/coveragepy/is … by-ctracer
.. _issue 179: \ 
https://bitbucket.org/ned/coveragepy/is … ce-file-is
.. _issue 183: \ 
https://bitbucket.org/ned/coveragepy/is … -python-23
.. _issue 194: \ 
https://bitbucket.org/ned/coveragepy/is … uld-mangle
.. _issue 195: \ 
https://bitbucket.org/ned/coveragepy/is … n-codeunit
.. _issue 197: \ 
https://bitbucket.org/ned/coveragepy/is … -not-align
.. _tox: http://tox.readthedocs.org/

Version 3.5.2 --- 4 May 2012
----------------------------

No changes since 3.5.2.b1

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`_ and `issue 142`_.

- 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: \ 
https://bitbucket.org/ned/coveragepy/is … tml-report
.. _issue 142: \ 
https://bitbucket.org/ned/coveragepy/is … s-replaced
.. _issue 155: \ 
https://bitbucket.org/ned/coveragepy/is … t-discover
.. _issue 157: \ 
https://bitbucket.org/ned/coveragepy/is … -non-utf-8
.. _issue 166: \ 
https://bitbucket.org/ned/coveragepy/is … on-on-pypy
.. _issue 168: \ 
https://bitbucket.org/ned/coveragepy/is … -droppings
.. _issue 173: \ 
https://bitbucket.org/ned/coveragepy/is … missing-in