Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
Name: python3-coverage | Distribution: SUSE Linux Enterprise 15 |
Version: 4.5.4 | Vendor: SUSE LLC <https://www.suse.com/> |
Release: 150000.3.3.2 | Build date: Fri May 20 17:10:47 2022 |
Group: Development/Languages/Python | Build host: sheep26 |
Size: 1220034 | Source RPM: python-coverage-4.5.4-150000.3.3.2.src.rpm |
Packager: https://www.suse.com/ | |
Url: https://github.com/nedbat/coveragepy | |
Summary: Code coverage measurement for Python |
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.
Apache-2.0
* Mon Mar 14 2022 adrian.glaubitz@suse.com - Update in SLE-15 (bsc#1195916, bsc#1196696, jsc#PM-3356, jsc#SLE-23972) * Fri Sep 13 2019 tchvatal@suse.com - Update to 4.5.4: * Multiprocessing support in Python 3.8 was broken, but is now fixed * Mon Mar 11 2019 tchvatal@suse.com - Update to 4.5.3: * Only packaging metadata changes. - Run fdupes * Tue Jan 01 2019 michael@stroeder.com - update to version 4.5.2: * Namespace packages are supported on Python 3.7 * Python 3.8 (as of today!) passes all tests * Tue Jul 17 2018 tchvatal@suse.com - Bumpy the URL to point to github rather than to docs * Sun Feb 18 2018 arun@gmx.de - update to version 4.5.1: * Now that 4.5 properly separated the [run] omit and [report] omit settings, an old bug has become apparent. If you specified a package name for [run] source, then omit patterns weren’t matched inside that package. This bug (issue 638) is now fixed. * On Python 3.7, reporting about a decorated function with no body other than a docstring would crash coverage.py with an IndexError (issue 640). This is now fixed. * Configurer plugins are now reported in the output of --debug=sys. * Sat Feb 10 2018 arun@gmx.de - specfile: * update copyright year - update to version 4.5: * A new kind of plugin is supported: configurators are invoked at start-up to allow more complex configuration than the .coveragerc file can easily do. See Plug-in classes for details. This solves the complex configuration problem described in issue 563. * The fail_under option can now be a float. Note that you must specify the [report] precision configuration option for the fractional part to be used. Thanks to Lars Hupfeldt Nielsen for help with the implementation. Fixes issue 631. * The include and omit options can be specified for both the [run] and [report] phases of execution. 4.4.2 introduced some incorrect interactions between those phases, where the options for one were confused for the other. This is now corrected, fixing issue 621 and issue 622. Thanks to Daniel Hahler for seeing more clearly than I could. * The coverage combine command used to always overwrite the data file, even when no data had been read from apparently combinable files. Now, an error is raised if we thought there were files to combine, but in fact none of them could be used. Fixes issue 629. * The coverage combine command could get confused about path separators when combining data collected on Windows with data collected on Linux, as described in issue 618. This is now fixed: the result path always uses the path separator specified in the [paths] result. * On Windows, the HTML report could fail when source trees are deeply nested, due to attempting to create HTML filenames longer than the 250-character maximum. Now filenames will never get much larger than 200 characters, fixing issue 627. Thanks to Alex Sandro for helping with the fix. * Thu Nov 09 2017 jmatejek@suse.com - test presence of python2 (not just if it is skipped; two different things now, unfortunately) * Mon Nov 06 2017 arun@gmx.de - update to version 4.4.2: * Support for Python 3.7. In some cases, class and module docstrings are no longer counted in statement totals, which could slightly change your total results. * Specifying both --source and --include no longer silently ignores the include setting, instead it displays a warning. Thanks, Loïc Dachary. Closes issue 265 and issue 101. * Fixed a race condition when saving data and multiple threads are tracing (issue 581). It could produce a “dictionary changed size during iteration” RuntimeError. I believe this mostly but not entirely fixes the race condition. A true fix would likely be too expensive. Thanks, Peter Baughman for the debugging, and Olivier Grisel for the fix with tests. * Configuration values which are file paths will now apply tilde-expansion, closing issue 589. * Now secondary config files like tox.ini and setup.cfg can be specified explicitly, and prefixed sections like [coverage:run] will be read. Fixes issue 588. * Be more flexible about the command name displayed by help, fixing issue 600. Thanks, Ben Finney. * Wed Oct 04 2017 arun@gmx.de - update to version 4.4.1: * No code changes: just corrected packaging for Python 2.7 Linux wheels. - changes from 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) - changes from version 4.4b1: * Some warnings can now be individually disabled. Warnings that can be disabled have a short name appended. The [run] disable_warnings setting takes a list of these warning names to disable. Closes both issue 96 and issue 355. * The XML report now includes attributes from version 4 of the Cobertura XML format, fixing issue 570. * In previous versions, calling a method that used collected data would prevent further collection. For example, save(), report(), html_report(), and others would all stop collection. An explicit start() was needed to get it going again. This is no longer true. Now you can use the collected data and also continue measurement. Both issue 79 and issue 448 described this problem, and have been fixed. * Plugins can now find unexecuted files if they choose, by implementing the find_executable_files method. Thanks, Emil Madsen. * Minimal IronPython support. You should be able to run IronPython programs under coverage run, though you will still have to do the reporting phase with CPython. * Coverage.py has long had a special hack to support CPython’s need to measure the coverage of the standard library tests. This code was not installed by kitted versions of coverage.py. Now it is. * Fri Aug 11 2017 toddrme2178@gmail.com - Handle cases where python2 is disabled (needed for SLE backports compatibility) * Wed Mar 29 2017 jmatejek@suse.com - uninstall alternatives in %postun * Mon Mar 13 2017 jmatejek@suse.com - update for singlespec - update to 4.3.4: - Using the --skip-covered option on an HTML report with 100% coverage would cause a “No data to report” error, as reported in issue 549. This is now fixed; thanks, Loïc Dachary. - If-statements can be optimized away during compilation, for example, if 0: or if __debug__:. Coverage.py had problems properly understanding these statements which existed in the source, but not in the compiled bytecode. This problem, reported in issue 522, is now fixed. - If you specified --source as a directory, then coverage.py would look for importable Python files in that directory, and could identify ones that had never been executed at all. But if you specified it as a package name, that detection wasn’t performed. Now it is, closing issue 426. Thanks to Loïc Dachary for the fix. - If you started and stopped coverage measurement thousands of times in your process, you could crash Python with a “Fatal Python error: deallocating None” error. This is now fixed. Thanks to Alex Groce for the bug report. - On PyPy, measuring coverage in subprocesses could produce a warning: “Trace function changed, measurement is likely wrong: None”. This was spurious, and has been suppressed. - Previously, coverage.py couldn’t start on Jython, due to that implementation missing the multiprocessing module (issue 551). This problem has now been fixed. Also, issue 322 about not being able to invoke coverage conveniently, seems much better: jython -m coverage run myprog.py works properly. - Let’s say you ran the HTML report over and over again in the same output directory, with --skip-covered. And imagine due to your heroic test-writing efforts, a file just acheived the goal of 100% coverage. With coverage.py 4.3, the old HTML file with the less-than-100% coverage would be left behind. This file is now properly deleted. * Sat Jan 14 2017 hpj@urpla.net - update to Version 4.3.1 — 2016-12-28: - Some environments couldn’t install 4.3, as described in issue 540. This is now fixed. - The check for conflicting --source and --include was too simple in a few different ways, breaking a few perfectly reasonable use cases, described in issue 541. The check has been reverted while we re-think the fix for issue 265. - update to Version 4.3 — 2016-12-27: Special thanks to Loïc Dachary, who took an extraordinary interest in coverage.py and contributed a number of improvements in this release. - The HTML report now supports a --skip-covered option like the other reporting commands. Thanks, Loïc Dachary for the implementation, closing issue 433. - Subprocesses that are measured with automatic subprocess measurement used to read in any pre-existing data file. This meant data would be incorrectly carried forward from run to run. Now those files are not read, so each subprocess only writes its own data. Fixes issue 510. - Coverage.py wouldn’t execute sys.excepthook when an exception happened in your program. Now it does, thanks to Andrew Hoos. Closes issue 535. - The coverage combine command will now fail if there are no data files to combine. The combine changes in 4.2 meant that multiple combines could lose data, leaving you with an empty .coverage data file. Fixes issues issue 525, issue 412, issue 516, and probably issue 511. - The branch coverage issues described in issue 493, issue 496, and issue 502 are now fixed, thanks to Loïc Dachary. - Options can now be read from a tox.ini file, if any. Like setup.cfg, sections are prefixed with “coverage:”, so [run] options will be read from the [coverage:run] section of tox.ini. Implements part of issue 519. Thanks, Stephen Finucane. - Specifying both --source and --include no longer silently ignores the include setting, instead it fails with a message. Thanks, Nathan Land and Loïc Dachary. Closes issue 265. - Coverage.py can now search .pex files for source, just as it can .zip and .egg. Thanks, Peter Ebden. * Tue Nov 15 2016 dmueller@suse.com - update to 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ä. * Mon Dec 28 2015 marec@detebe.org - update to 4.0.3: - Fixed a mysterious problem that manifested in different ways: sometimes hanging the process (`issue 420`_), sometimes making database connections fail (`issue 445`_). - The XML report now has correct ``<source>`` elements when using a ``--source=`` option somewhere besides the current directory. This fixes `issue 439`_. Thanks, Arcady Ivanov. - Fixed an unusual edge case of detecting source encodings, described in `issue 443`_. - Help messages that mention the command to use now properly use the actual command name, which might be different than "coverage". Thanks to Ben Finney, this closes `issue 438`_. * Sat Oct 31 2015 dmueller@suse.com - add LICENSE.txt * Fri Oct 16 2015 bgeuken@suse.com - Pre require coreutils. This package is needed for the rm call in the pre section. Subprocess failed. Error: RPM failed: /var/tmp/rpm-tmp.gONanE: line 3: rm: command not found * Wed Oct 07 2015 arun@gmx.de - specfile: * updated license * updated update-alternatives * README.txt -> README.rst - update to version 4.0: (long list, see http://coverage.readthedocs.org/en/latest/changes.html) * Fri Jul 24 2015 seife+obs@b1-systems.com - fix rhel deps by depending on /usr/sbin/update-alternatives * Sun Nov 09 2014 ledest@gmail.com - fix bashism in pre script
/etc/alternatives/coverage /usr/bin/coverage /usr/bin/coverage-3.6 /usr/bin/coverage3 /usr/lib64/python3.6/site-packages/coverage /usr/lib64/python3.6/site-packages/coverage-4.5.4-py3.6.egg-info /usr/lib64/python3.6/site-packages/coverage-4.5.4-py3.6.egg-info/PKG-INFO /usr/lib64/python3.6/site-packages/coverage-4.5.4-py3.6.egg-info/SOURCES.txt /usr/lib64/python3.6/site-packages/coverage-4.5.4-py3.6.egg-info/dependency_links.txt /usr/lib64/python3.6/site-packages/coverage-4.5.4-py3.6.egg-info/entry_points.txt /usr/lib64/python3.6/site-packages/coverage-4.5.4-py3.6.egg-info/not-zip-safe /usr/lib64/python3.6/site-packages/coverage-4.5.4-py3.6.egg-info/top_level.txt /usr/lib64/python3.6/site-packages/coverage/__init__.py /usr/lib64/python3.6/site-packages/coverage/__main__.py /usr/lib64/python3.6/site-packages/coverage/__pycache__ /usr/lib64/python3.6/site-packages/coverage/__pycache__/__init__.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/__init__.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/__main__.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/__main__.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/annotate.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/annotate.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/backunittest.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/backunittest.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/backward.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/backward.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/bytecode.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/bytecode.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/cmdline.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/cmdline.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/collector.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/collector.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/config.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/config.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/control.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/control.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/data.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/data.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/debug.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/debug.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/env.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/env.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/execfile.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/execfile.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/files.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/files.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/html.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/html.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/misc.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/misc.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/multiproc.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/multiproc.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/parser.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/parser.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/phystokens.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/phystokens.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/pickle2json.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/pickle2json.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/plugin.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/plugin.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/plugin_support.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/plugin_support.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/python.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/python.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/pytracer.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/pytracer.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/report.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/report.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/results.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/results.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/summary.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/summary.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/templite.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/templite.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/version.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/version.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/xmlreport.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/__pycache__/xmlreport.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/annotate.py /usr/lib64/python3.6/site-packages/coverage/backunittest.py /usr/lib64/python3.6/site-packages/coverage/backward.py /usr/lib64/python3.6/site-packages/coverage/bytecode.py /usr/lib64/python3.6/site-packages/coverage/cmdline.py /usr/lib64/python3.6/site-packages/coverage/collector.py /usr/lib64/python3.6/site-packages/coverage/config.py /usr/lib64/python3.6/site-packages/coverage/control.py /usr/lib64/python3.6/site-packages/coverage/data.py /usr/lib64/python3.6/site-packages/coverage/debug.py /usr/lib64/python3.6/site-packages/coverage/env.py /usr/lib64/python3.6/site-packages/coverage/execfile.py /usr/lib64/python3.6/site-packages/coverage/files.py /usr/lib64/python3.6/site-packages/coverage/fullcoverage /usr/lib64/python3.6/site-packages/coverage/fullcoverage/__pycache__ /usr/lib64/python3.6/site-packages/coverage/fullcoverage/__pycache__/encodings.cpython-36.opt-1.pyc /usr/lib64/python3.6/site-packages/coverage/fullcoverage/__pycache__/encodings.cpython-36.pyc /usr/lib64/python3.6/site-packages/coverage/fullcoverage/encodings.py /usr/lib64/python3.6/site-packages/coverage/html.py /usr/lib64/python3.6/site-packages/coverage/htmlfiles /usr/lib64/python3.6/site-packages/coverage/htmlfiles/coverage_html.js /usr/lib64/python3.6/site-packages/coverage/htmlfiles/index.html /usr/lib64/python3.6/site-packages/coverage/htmlfiles/jquery.ba-throttle-debounce.min.js /usr/lib64/python3.6/site-packages/coverage/htmlfiles/jquery.hotkeys.js /usr/lib64/python3.6/site-packages/coverage/htmlfiles/jquery.isonscreen.js /usr/lib64/python3.6/site-packages/coverage/htmlfiles/jquery.min.js /usr/lib64/python3.6/site-packages/coverage/htmlfiles/jquery.tablesorter.min.js /usr/lib64/python3.6/site-packages/coverage/htmlfiles/keybd_closed.png /usr/lib64/python3.6/site-packages/coverage/htmlfiles/keybd_open.png /usr/lib64/python3.6/site-packages/coverage/htmlfiles/pyfile.html /usr/lib64/python3.6/site-packages/coverage/htmlfiles/style.css /usr/lib64/python3.6/site-packages/coverage/misc.py /usr/lib64/python3.6/site-packages/coverage/multiproc.py /usr/lib64/python3.6/site-packages/coverage/parser.py /usr/lib64/python3.6/site-packages/coverage/phystokens.py /usr/lib64/python3.6/site-packages/coverage/pickle2json.py /usr/lib64/python3.6/site-packages/coverage/plugin.py /usr/lib64/python3.6/site-packages/coverage/plugin_support.py /usr/lib64/python3.6/site-packages/coverage/python.py /usr/lib64/python3.6/site-packages/coverage/pytracer.py /usr/lib64/python3.6/site-packages/coverage/report.py /usr/lib64/python3.6/site-packages/coverage/results.py /usr/lib64/python3.6/site-packages/coverage/summary.py /usr/lib64/python3.6/site-packages/coverage/templite.py /usr/lib64/python3.6/site-packages/coverage/tracer.cpython-36m-x86_64-linux-gnu.so /usr/lib64/python3.6/site-packages/coverage/version.py /usr/lib64/python3.6/site-packages/coverage/xmlreport.py /usr/share/doc/packages/python3-coverage /usr/share/doc/packages/python3-coverage/CHANGES.rst /usr/share/doc/packages/python3-coverage/CONTRIBUTORS.txt /usr/share/doc/packages/python3-coverage/README.rst /usr/share/doc/packages/python3-coverage/TODO.txt /usr/share/doc/packages/python3-coverage/howto.txt /usr/share/licenses/python3-coverage /usr/share/licenses/python3-coverage/LICENSE.txt
Generated by rpm2html 1.8.1
Fabrice Bellet, Tue Jul 9 18:11:13 2024