I really don't like this. The `print` statement isn't going to log anywhere useful (use the `logging` module for that). The return value is utterly unhelpful, and the program will probably continue chugging merrily along assuming that everything worked well until it tries to access some data from that return value, and trips over itself when there's no data to access. Either handle the failure gracefully at a higher level, or let it fail as quickly and as noisily as possible so that it's easier to understand where the failure is coming from and how to fix it.