2970bbcf03
Version 4.2 ------------ - Since concurrency=multiprocessing uses subprocesses, options specified on the coverage.py command line will not be communicated down to them. Only options in the configuration file will apply to the subprocesses. Previously, the options didn't apply to the subprocesses, but there was no indication. Now it is an error to use --concurrency=multiprocessing and other run-affecting options on the command line. This prevents failures like those reported in issue 495. - Filtering the HTML report is now faster, thanks to Ville Skyttä. Version 4.2b1 ------------- Work from the PyCon 2016 Sprints! - BACKWARD INCOMPATIBILITY: the coverage combine command now ignores an existing .coverage data file. It used to include that file in its combining. This caused confusing results, and extra tox "clean" steps. If you want the old behavior, use the new coverage combine --append option. - The concurrency option can now take multiple values, to support programs using multiprocessing and another library such as eventlet. This is only possible in the configuration file, not from the command line. The configuration file is the only way for sub-processes to all run with the same options. - Using a concurrency setting of multiprocessing now implies --parallel so that the main program is measured similarly to the sub-processes. - When using automatic subprocess measurement, running coverage commands would create spurious data files. This is now fixed. - A new configuration option, report:sort, controls what column of the text report is used to sort the rows. - The HTML report has a more-visible indicator for which column is being sorted. - If the HTML report cannot find the source for a file, the message now suggests using the -i flag to allow the report to continue. - When reports are ignoring errors, there's now a warning if a file cannot be parsed, rather than being silently ignored. - A new option for coverage debug is available: coverage debug config shows the current configuration. - Running coverage as a module (python -m coverage) no longer shows the program name as __main__.py. - The test_helpers module has been moved into a separate pip-installable package: unittest-mixins. |
||
|---|---|---|
| .. | ||
| README.md | ||
| requirements-check-manifest.txt | ||
| requirements-check-manifest.txt-raw | ||
| requirements-codecov.txt | ||
| requirements-codecov.txt-raw | ||
| requirements-cxfreeze.txt | ||
| requirements-cxfreeze.txt-raw | ||
| requirements-flake8.txt | ||
| requirements-flake8.txt-raw | ||
| requirements-pip.txt | ||
| requirements-pyinstaller.txt | ||
| requirements-pyinstaller.txt-raw | ||
| requirements-pylint-master.txt | ||
| requirements-pylint-master.txt-raw | ||
| requirements-pylint.txt | ||
| requirements-pylint.txt-raw | ||
| requirements-pyroma.txt | ||
| requirements-pyroma.txt-raw | ||
| requirements-qutebrowser.txt-raw | ||
| requirements-tests.txt | ||
| requirements-tests.txt-raw | ||
| requirements-tox.txt | ||
| requirements-tox.txt-raw | ||
| requirements-vulture.txt | ||
| requirements-vulture.txt-raw | ||
This directory contains various requirements files which are used by tox to
have reproducable tests with pinned versions.
The files are generated based on unpinned requirements in *.txt-raw files.
Those files can also contain some special commands:
- Add an additional comment to a line:
#@ comment: <package> <comment here> - Filter a line for requirements.io:
#@ filter: <package> <filter> - Don't include a package in the output:
#@ ignore: <package>(or multiple packages) - Replace a part of a frozen package specification with another:
#@ replace <regex> <replacement>
Some examples:
#@ comment: mypkg blah blub
#@ filter: mypkg != 1.0.0
#@ ignore: mypkg, otherpkg
#@ replace: foo bar