From f1e080b7afac74c736e69f4be8d4610d18d679fe Mon Sep 17 00:00:00 2001 From: JoeLametta Date: Mon, 4 Jul 2016 10:13:41 +0200 Subject: [PATCH] Logger cosmetic fixes (again) Missing line break, consistent AccurateRip summary result output. --- morituri/result/logger.py | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/morituri/result/logger.py b/morituri/result/logger.py index a78626a..10401e7 100644 --- a/morituri/result/logger.py +++ b/morituri/result/logger.py @@ -68,6 +68,7 @@ class MorituriLogger(result.Logger): lines.append(" Length: %s" % common.framesToMSF(htoalength)) lines.append(" Start sector: %d" % htoastart) lines.append(" End sector: %d" % htoaend) + lines.append("") for t in table.tracks: # FIXME: what happens to a track start over 60 minutes ? # Answer: tested empirically, everything seems OK @@ -104,11 +105,6 @@ class MorituriLogger(result.Logger): "accurate (you may have a different pressing " "from the one(s) in the database") elif self._accuratelyRipped < nonHTOA: - lines.append(" %d track(s) accurately ripped" % - self._accuratelyRipped) - lines.append(" %d track(s) could not be verified as " - "accurate" % (nonHTOA - self._accuratelyRipped)) - lines.append("") lines.append(" Result: Some tracks could not be verified " "as accurate (%d/%d got no match)" % ( (nonHTOA - self._accuratelyRipped), nonHTOA))