coverage-5.0.2
·
1936 commits
to master
since this release
- Programs that used multiprocessing and changed directories would fail under coverage. This is now fixed (issue 890). A side effect is that debug information about the config files read now shows absolute paths to the files.
- When running programs as modules (
coverage run -m) with--source, some measured modules were imported before coverage starts. This resulted in unwanted warnings (“Already imported a file that will be measured”) and a reduction in coverage totals (issue 909). This is now fixed. - If no data was collected, an exception about “No data to report” could happen instead of a 0% report being created (issue 884). This is now fixed.
- The handling of source files with non-encodable file names has changed. Previously, if a file name could not be encoded as UTF-8, an error occurred, as described in issue 891. Now, those files will not be measured, since their data would not be recordable.
- A new warning (“dynamic-conflict”) is issued if two mechanisms are trying to change the dynamic context. Closes issue 901.
coverage run --debug=syswould fail with an AttributeError. This is now fixed (issue 907).