python-coverage
http://pypi.python.org/coverage
Coverage.py measures code coverage, typically during test 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.
- Devel package for openSUSE:Factory
-
15
derived packages
- Links to openSUSE:Factory / python-coverage
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:languages:python/python-coverage && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_link | 0000000150 150 Bytes | |
coverage-7.0.1.tar.gz | 0000781226 763 KB | |
python-coverage.changes | 0000049279 48.1 KB | |
python-coverage.spec | 0000003862 3.77 KB |
Revision 104 (latest revision is 132)
- Update to 7.0.1 * When checking if a file mapping resolved to a file that exists, we weren’t considering files in .whl files. This is now fixed, closing issue 1511. * File pattern rules were too strict, forbidding plus signs and curly braces in directory and file names. This is now fixed, closing issue 1513. * Unusual Unicode or control characters in source files could prevent reporting. This is now fixed, closing issue 1512. * The PyPy wheel now installs on PyPy 3.7, 3.8, and 3.9, closing issue 1510. - Release 7.0.0 * Changes to file pattern matching, which might require updating your configuration: - Previously, * would incorrectly match directory separators, making precise matching difficult. This is now fixed, closing issue 1407. - Now ** matches any number of nested directories, including none. * Improvements to combining data files when using the [run] relative_files setting, which might require updating your configuration: - During coverage combine, relative file paths are implicitly combined without needing a [paths] configuration setting. This also fixed issue 991. - A [paths] setting like */foo will now match foo/bar.py so that relative file paths can be combined more easily. - The [run] relative_files setting is properly interpreted in more places, fixing issue 1280. * When remapping file paths with [paths], a path will be remapped
Comments 0