why swallow the errors with a print statement? a Pythonic design idea is "crash early and often" i.e. just let the exception happen and get your stack trace so you can debug. handle exceptions where handling it means doing something that doesn't break control flow.
-
-
in Python, working with the language means just let exceptions happen and let the program crash and give you a stacktrace. wrapping things in a try/except block should be done only with specific exceptions (e.g. no except Exception catches, the infamous "Pokemon error handling)
-
Tweet unavailable
-
yeah, that's exactly what I mean by working with the language. where to find more? I'm not the greatest person to ask since I'm basically just a humble webshit "engineer" and not deeply connected in the python language community. check the usual internet spots I guess.
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.