THIS Broke My Code In Python #python #code #programming

This broke my code in Python. #python #code #programming

[tutorialsandgaminghelp]

That is because you're not supposed to return anything from the finally block. It's mainly meant to clean up any side effects such as closing a file or aborting a network request.

[kellymoses]

putting a return in the finally block should be a syntax error.

[BenMeddeb]

finally works that way in every language not just python

[NeumsFor]

That's what I like to call a 5 o clock error 😂

[skylarscott]

I didn't know this. I do a lot of C++ and this is an insanely nice feature for writing failure safe code. You won't normally use returns here, but you will be able to run "undo" steps in the finally block if you run into an exception. It's like RAII (guard scope) without creating an object.

[PhrontDoor]

return is supposed to LEAVE the entire function.
But I love the weasel excuse in the docs :
"When  passes control out of a  statement with a  clause, that  clause is executed before REALLY leaving the function."

[chrono]

You do realize the finally block is supposed to be used to clean up work such as closing files. You are supposed to return the value in either the try and except part of the statement. The finally will run regardless of when the return happens. That's the point of it.

[Mathman]

Instead of using finally here, you can use else, which means it only runs if no error happens.

[thealex]

British people be like:
this pheechu ... 😂

[callbettersaul]

"This feature recently broke my code in python". Did you just make this up or did you actually write this for some reason?

[scottcampbell]

So does this mean that the "return 0" statement just gets ignored? If the finally block just had a print("foo") instead of return, would it return 0?

[MyCodingDiary]

You have a gift for teaching. Truly remarkable!

[five-toedslothbear]

The feature didn’t break your code. Your code was already broken. The action of returning from a finally block is a code smell that is so widely known, that it is encoded in various linters such as Ruff, as SIM107. Such code checkers contain the accumulated wisdom of many developers, and the real lesson from this video would be to use them.

[igorfujs]

Return statement should be forbiden in catch/finally block

[abdullahsaid]

now I understand this finally finally...👌👌👌

[KeithKazamaFlick]

its called finally ... cant be anymore clearer than that.
its ment for use with context managers.
use else instead

[asagiai]

In most PL I believe finally is the last to execute. the weird thing is if you use return statement it should ended it right away.
The fact that it isn't mean there's something wrong.
In the language I'm using it won't allow you to use return on finally.

[BBCCheese]

I think you meant to use 'else' here instead of finally

[sergeibatiuk]

Do you return values from finally? Face the consequences

[astromec]

Surely that must be a bug right? Because that’s not supposed to do that right? Shouldn’t the “finally” block be unreachable in that case?