From b82e9fd8766a77c2a275bde7b574f3e8cb529f8f Mon Sep 17 00:00:00 2001 From: Ned Batchelder Date: Sat, 13 Nov 2021 19:23:24 -0500 Subject: refactor: specialize exceptions CoverageException is fine as a base class, but not good to use for raising (and catching sometimes). Introduce specialized exceptions that allow third-party tools to integrate better. --- coverage/summary.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'coverage/summary.py') diff --git a/coverage/summary.py b/coverage/summary.py index 0b54a05b..467c601d 100644 --- a/coverage/summary.py +++ b/coverage/summary.py @@ -5,7 +5,7 @@ import sys -from coverage.exceptions import CoverageException +from coverage.exceptions import ConfigError, NoDataError from coverage.misc import human_sorted_items from coverage.report import get_analysis_to_report from coverage.results import Numbers @@ -103,7 +103,7 @@ class SummaryReporter: else: position = column_order.get(sort_option) if position is None: - raise CoverageException(f"Invalid sorting option: {self.config.sort!r}") + raise ConfigError(f"Invalid sorting option: {self.config.sort!r}") lines.sort(key=lambda l: (l[1][position], l[0]), reverse=reverse) for line in lines: @@ -122,7 +122,7 @@ class SummaryReporter: # Write other final lines. if not self.total.n_files and not self.skipped_count: - raise CoverageException("No data to report.") + raise NoDataError("No data to report.") if self.config.skip_covered and self.skipped_count: self.writeout( -- cgit v1.2.1