It's not technically an error, but one of the most common issues I encountered when I was first learning python was returning None when I thought I was returning something valid.
finally block runs regardless of if you ran except or not but still before returning or raising an exception eg try: return 1 finally: print("this still runs even though you returned") useful for closing resources regardless of what happens
It's not technically an error, but one of the most common issues I encountered when I was first learning python was returning None when I thought I was returning something valid.
Thanks for your all these tutorials! Very well done
Why do we use -> in function definition, is it return data type?
Yes, it's a hint for the return type
Very good, thanks a lot.
The KeyError description is so descriptive 😂
I’m a bit shocked they didn’t update that 😂
For the very least they could write: key not found
awesome and clear ; thanks a lot
Useful content. THX 👍
Can you create a video on how to perform logging with multiprocessing? please
i always use try except to fix my errors
does anyone know what the finally block does in python
finally block runs regardless of if you ran except or not but still before returning or raising an exception
eg
try:
return 1
finally:
print("this still runs even though you returned")
useful for closing resources regardless of what happens
@@kenzostaelens1688
Thanks
Very much appreciated
Sir macbook air M1 for app development is ok? Please help
Works for me
Bro do a video on subprocess error