coverage.control.Coverage.data_suffix has been removed in 5.0.0, but is not in the release notes
See original GitHub issueThe .data_suffix
attribute on Coverage
instances has been removed. This change isn’t documented in the release notes.
Causes https://github.com/computationalmodelling/nbval/issues/129
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Major changes in 5.0 — Coverage.py 6.5.0 documentation
Using it will result in a warning, and the note will not be written to the data file. The corresponding CoverageData methods have...
Read more >coveragepy/CHANGES.rst at master - GitHub
An empty file has a coverage total of 100%, but used to fail with --fail-under . ... The deprecated [run] note setting has...
Read more >Code coverage generation fails on … | Apple Developer Forums
Resulting in coverage data missing for our project. Has anyone else encountered this? Known issue? Any workarounds? Thanks in advance for any help....
Read more >Unexpected Coverage Changes - Codecov
There are many reasons why coverage may change in unexpected ways. Centrally, these occur in files that are not directly changed in the...
Read more >Release Notes Last Updated February 10, 2022 - TechDocs
This section summarizes the new or updated functionalities and known issues of CA Agile Requirements Designer 3.1, and the 3.1.1 patch.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I added some warnings and admonitions in 3875113f0e8a8ec333b61000fbe038a2725903f4
I guess I should be more disciplined. I didn’t consider any of the data attributes of Coverage to be part of the publicly supported interface, since they aren’t documented.
In 5.0 they have underscore prefixes. I can clarify this.