From ffd9289edc5bab32e1e2314e7c04b4da9c933867 Mon Sep 17 00:00:00 2001 From: JustAnotherArchivist Date: Sun, 11 Oct 2020 22:29:27 +0000 Subject: [PATCH] Reduce the logging level of retryable retrieval errors from WARNING to INFO There is no real need to report these as WARNINGs as snscrape tries and in most cases manages to recover. Without --verbose, snscrape's output can be confusing (see #76). If the retries fail as well, snscrape will still log that as an ERROR and crash loudly. --- snscrape/base.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/snscrape/base.py b/snscrape/base.py index 83d9d07..714e23e 100644 --- a/snscrape/base.py +++ b/snscrape/base.py @@ -89,7 +89,7 @@ class Scraper: except requests.exceptions.RequestException as exc: if attempt < self._retries: retrying = ', retrying' - level = logging.WARNING + level = logging.INFO else: retrying = '' level = logging.ERROR @@ -107,7 +107,7 @@ class Scraper: else: if attempt < self._retries: retrying = ', retrying' - level = logging.WARNING + level = logging.INFO else: retrying = '' level = logging.ERROR