bellingcat/snscrape
1
0
Fork 0
mirror of https://github.com/bellingcat/snscrape.git synced 2026-06-13 12:58:27 +03:00
Code Issues Packages Projects Releases Wiki Activity

Reduce the logging level of retryable retrieval errors from WARNING to INFO

Browse Source 
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.
This commit is contained in:
JustAnotherArchivist
2020-10-11 22:29:27 +00:00
parent b1a7b9607f
commit ffd9289edc
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
snscrape/base.py
View File

@@ -89,7 +89,7 @@ class Scraper:
except requests.exceptions.RequestException as exc: except requests.exceptions.RequestException as exc:
if attempt < self._retries: if attempt < self._retries:
retrying = ', retrying' retrying = ', retrying'
level = logging.WARNING level = logging.INFO
else: else:
retrying = '' retrying = ''
level = logging.ERROR level = logging.ERROR
@@ -107,7 +107,7 @@ class Scraper:
else: else:
if attempt < self._retries: if attempt < self._retries:
retrying = ', retrying' retrying = ', retrying'
level = logging.WARNING level = logging.INFO
else: else:
retrying = '' retrying = ''
level = logging.ERROR level = logging.ERROR