Finally always executes. That’s what it’s for, which means its return value gets used in your case. You’ll want to change your code so it’s more like this: function example() { var returnState = false; // initialization value is really up to the design try { returnState = true; } catch { returnState = false; … Read more
The try block completes with the execution of the return statement and the value of s at the time the return statement executes is the value returned by the method. The fact that the finally clause later changes the value of s (after the return statement completes) does not (at that point) change the return … Read more
It doesn’t run forever. Each stack overflow causes the code to move to the finally block. The problem is that it will take a really, really long time. The order of time is O(2^N) where N is the maximum stack depth. Imagine the maximum depth is 5 foo() calls foo() calls foo() calls foo() calls … Read more
It makes a difference if you return early: try: run_code1() except TypeError: run_code2() return None # The finally block is run before the method returns finally: other_code() Compare to this: try: run_code1() except TypeError: run_code2() return None other_code() # This doesn’t get run if there’s an exception. Other situations that can cause differences: If an … Read more