<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 3, 2015 at 6:32 AM, Doug Hellmann <span dir="ltr"><<a href="mailto:doug@doughellmann.com" target="_blank">doug@doughellmann.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Do we have anyone willing to spend some time looking at the<br>
incompatibilities Ned mentions below to ensure that we have a smooth<br>
transition when 4.0 moves out of alpha?<br>
<br>
Doug<br>
<br></blockquote><div><br></div><div>Seems to work ok with keystone. There were a couple of problems running it but they were easy to work around.<br><br>When starting, "Unrecognized option '[report] ignore-errors=' in config file .coveragerc"; removed the section and didn't get the error:<br>-<br>-[report]<br>-ignore-errors = True<br><br>At end of run, "Couldn't read data from '/opt/stack/keystone/.coverage': CoverageException: Doesn't seem to be a coverage.py data file"; deleted .coverage and ran again, I think it was left over from old run.<br><br>Results are like:<br>Old summary: Total 16846 1442 194 4239 434 90%<br>New summary: Total 16846 1442 194 4239 435 90%<br></div><div>it found another "Partial" line somewhere.<br></div><div><br></div><div>-- Brant<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
--- Begin forwarded message from Ned Batchelder ---<br>
From: Ned Batchelder <<a href="mailto:ned@nedbatchelder.com">ned@nedbatchelder.com</a>><br>
To: testing-in-python <<a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a>><br>
Date: Mon, 03 Aug 2015 07:22:30 -0400<br>
Subject: [TIP] Coverage.py 4.0 beta 1<br>
<br>
Hi all,<br>
<br>
After more than 18 months of development, the first beta of Coverage.py<br>
4.0 is available: <a href="https://pypi.python.org/pypi/coverage/4.0b1" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/coverage/4.0b1</a><br>
<br>
There are a number of very significant changes since v3.7.1, including<br>
backward-incompatibilities. I'd really appreciate getting some testing<br>
from people using third-party coverage integrations, or using unusual<br>
configurations.<br>
<br>
Bug reports heartily welcomed: <a href="https://bitbucket.org/ned/coveragepy" rel="noreferrer" target="_blank">https://bitbucket.org/ned/coveragepy</a><br>
<br>
A quick list of the biggest changes are below, more at<br>
<a href="http://coverage.readthedocs.org/en/coverage-4.0b1/changes.html" rel="noreferrer" target="_blank">http://coverage.readthedocs.org/en/coverage-4.0b1/changes.html</a><br>
<br>
Thanks,<br>
<br>
--Ned.<br>
<br>
<br>
<br>
Backward incompatibilities:<br>
<br>
- CPython versions supported are now Python 2.6, 2.7, 3.3, 3.4 and 3.5b4.<br>
PyPy2 2.4, 2.6, and PyPy3 2.4 are also supported.<br>
<br>
- The original command line switches (`-x` to run a program, etc) are no<br>
longer supported.<br>
<br>
- The ``COVERAGE_OPTIONS`` environment variable is no longer supported.<br>
It was<br>
a hack for ``--timid`` before configuration files were available.<br>
<br>
- The original module-level function interface to coverage.py is no longer<br>
supported. You must now create a ``coverage.Coverage`` object, and use<br>
methods on it.<br>
<br>
- The ``Coverage.use_cache`` method is no longer supported.<br>
<br>
- The private method ``Coverage._harvest_data`` is now called<br>
``Coverage.get_data``, and returns the ``CoverageData`` containing the<br>
collected data.<br>
<br>
- Coverage.py is now licensed under the Apache 2.0 license. See<br>
NOTICE.txt for<br>
details.<br>
<br>
<br>
Major new features:<br>
<br>
- Plugins: third parties can write plugins to add file support for<br>
non-Python<br>
files, such as web application templating engines, or languages that<br>
compile<br>
down to Python. A plugin for measuring Django template coverage is<br>
available: `django_coverage_plugin`_<br>
<br>
- The data storage has been re-written, using JSON instead of pickle. The<br>
:class:`CoverageData` class is a new supported API to the contents of the<br>
data file.<br>
<br>
- Gevent, eventlet, and greenlet are now supported, closing `issue<br>
149`_. The<br>
``concurrency`` setting, or the ``--concurrency`` command line switch,<br>
specifies the concurrency library in use. Huge thanks to Peter<br>
Portante for<br>
initial implementation, and to Joe Jevnik for the final insight that<br>
completed the work.<br>
<br>
- Wildly experimental: support for measuring processes started by the<br>
multiprocessing module. To use, set ``--concurrency=multiprocessing``,<br>
either on the command line or in the .coveragerc file (`issue 117`_).<br>
Thanks,<br>
Eduardo Schettino. Currently, this does not work on Windows.<br>
<br>
<br>
New features:<br>
<br>
- Options are now also read from a setup.cfg file, if any. Sections are<br>
prefixed with "coverage:", so the ``[run]`` options will be read from the<br>
``[coverage:run]`` section of setup.cfg. Finishes `issue 304`_.<br>
<br>
- A new option: `coverage report --skip-covered` (or ``[report]<br>
skip_covered``)<br>
will reduce the number of files reported by skipping files with 100%<br>
coverage. Thanks, Krystian Kichewko. This means that empty<br>
`__init__.py`<br>
files will be skipped, since they are 100% covered, closing `issue 315`_.<br>
<br>
- You can now specify the ``--fail-under`` option in the ``.coveragerc``<br>
file<br>
as the ``[report] fail_under`` options. This closes `issue 314`_.<br>
<br>
- The ``report`` command can now show missing branches when reporting on<br>
branch<br>
coverage. Thanks, Steve Leonard. Closes `issue 230`_.<br>
<br>
- The ``coverage combine`` command now accepts any number of directories or<br>
files as arguments, and will combine all the data from them. This<br>
means you<br>
don't have to copy the files to one directory before combining. Thanks,<br>
Christine Lytwynec. Finishes `issue 354`_.<br>
<br>
- A new configuration option for the XML report: ``[xml] package_depth``<br>
controls which directories are identified as packages in the report.<br>
Directories deeper than this depth are not reported as packages.<br>
The default is that all directories are reported as packages.<br>
Thanks, Lex Berezhny.<br>
<br>
- A new configuration option, ``[run] note``, lets you set a note that<br>
will be<br>
stored in the `runs` section of the data file. You can use this to<br>
annotate<br>
the data file with any information you like.<br>
<br>
- The COVERAGE_DEBUG environment variable can be used to set the ``[run]<br>
debug``<br>
configuration option to control what internal operations are logged.<br>
<br>
--- End forwarded message ---<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div></div>