Yes, exception handling and exiting application should be moved from library to executable (bin/GetOldTweets). I can merge your PR after you add the exceptions handling to a new place.

Yes, exception handling and exiting application should be moved from library to executable (bin/GetOldTweets). I can merge your PR after you add the exceptions handling to a new place.

What about pushing some errors up to the user (especially the http exceptions)?

The most common errors here are Limit exceptions from Twitter itself - if we push them up to the user we can handle them and continue the execution e.g. after a short delay w/o manual interaction.

An error occured during an HTTP request: HTTP Error 429: Too Many Requests

+1 to this. I wasn't aware of it and my entire application was crashing just because a 1% part of it was using this library to read some twits in another thread. Please never call sys.exit() on a library that it is supposed to be imported, as it will often be used as just 1 more module of a bigger application, and that module/thread alone shouldn't crash the entire application.