loop_forever should really loop_forever

Or, document that it could throw exceptions. If it's meant to handle reconnections, perhaps it should have a try: except block inside the loop_forever call? Arguably that's too invasive, and doesn't allow any escape hatch, but for a method documented as "handles everything, blocks forever" it still has chances of exceptions that are not obvious at first view.

Heavily related to #112