Great article. Would not have guessed that try...except would be more efficient than if/else in cases like you mentioned, although that makes sense.
Any idea what the logic is for having finally: run regardless of returns?
Great info about "except WhateverError as e:" and "raise from".
Edit: Also always great reading the informative comments, both interesting questions and answers!
finally always runs to ensure cleanup/teardown behavior runs. It comes in handy surprisingly often.
finally
Also, whether try or if is more efficient is really really subjective. If it matters, always measure.
try
if
Good point. But good to even be aware of the idea!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great article. Would not have guessed that try...except would be more efficient than if/else in cases like you mentioned, although that makes sense.
Any idea what the logic is for having finally: run regardless of returns?
Great info about "except WhateverError as e:" and "raise from".
Edit: Also always great reading the informative comments, both interesting questions and answers!
finally
always runs to ensure cleanup/teardown behavior runs. It comes in handy surprisingly often.Also, whether
try
orif
is more efficient is really really subjective. If it matters, always measure.Good point. But good to even be aware of the idea!