Hi,
Currently, running query_tweets prints a large number of logs, which sometimes crash the browser session (for eg. if you use Google Colab) especially if you are iterating over a list of keywords. Additionally, it is not exactly a pretty way to visualize progress if you are iterating over several keywords.
By keeping the logger mode as a parameter (eg. verbose, etc.) rather than fixed to logger.INFO in ts.logger, we can solve this issue.
Thanks
Hi, Currently, running query_tweets prints a large number of logs, which sometimes crash the browser session (for eg. if you use Google Colab) especially if you are iterating over a list of keywords. Additionally, it is not exactly a pretty way to visualize progress if you are iterating over several keywords. By keeping the logger mode as a parameter (eg. verbose, etc.) rather than fixed to logger.INFO in ts.logger, we can solve this issue. Thanks