5 Useful Python Decorators (ft. Carberra)
2024 ж. 13 Мам.
78 155 Рет қаралды
Here are 5 useful decorators that can help make your code more convenient to use! And a big thanks @Carberra for joining in on this video; do check him out if you love Python!
Check out Carberra:
/ @carberra
Github repository:
github.com/federicoazzu/five_...
▶ Become job-ready with Python:
www.indently.io
▶ Follow me on Instagram:
/ indentlyreels
00:00 Learning Python made simple
00:05 Intro
00:32 @retry
02:42 Sponsor
02:52 @cache
05:50 @get_time
07:51 @deprecated
10:58 @on_exit
13:51 Amazing
Congratulations on getting the sponsorship deal!
Thanks, they're very easy to work with! Absolutely recommend them :)
I’m actually dating them rn. Like right. Now.
I just can’t deal with type annotations on an add function. Is this not DEVOlution ? Next we’ll be calling it “addi”, with “addf”, “adds”, “addl”…..I can keep going…addc,
Very nice collab! The deprecated decorator was a very much necessary functionality, especially for libraries. Coming from a Java background, not having this decorator in the main Python language surprised me.
May I ask what you do mean by that? Because Java indeed has one. You could argue with me that the semantics are not the same but syntactically they are the same ^^.
When it comes to retries, you may want to have a look at the Tenacity library. E.g. Tenacity allows for random wait times, exponential wait times or even only retrying for certain exception types.
Also has a cool name!
yep, certain exception is great. Catching any excepting is just nasty
One of the best uses of the cache decorator is in recursive functions. Every recursive call get's cached, meaning if you call factorial(n) and then factorial(n+2), only 2 extra recursive calls will be made, for a total of n+2 calls. Any call to factorial(m) for m =< n will also be entirely cached.
Fibonacci is the go-to function for demonstrating the cache decorator.
What would be a good demo is some use cases that demonstrate the advantages of @cache vs @lru_cache versus each other. When to use each.
If you input numbers like 1000 you get a RecursionError. Also isn't it
@@cycrothelargeplanetyou can change the limit with the sys module
Tenacity’s retry decorator is really good and quite expressive. Atexit: use a context manager with a try/finally block to close that database for most applications. Atexit mainly applies to long running python programs that are run as a server or daemon.
Simply the best videos for people learning Python. You're a highly effective communicator who has a teaching spirit. Thank you for helping!
Thanks for the kind words :)
I've also written the retry and the timing decorators a few times for various projects, I wish it were standardized in a built-in module
Some code that might be useful to my project, a source that looks well worthy of a sub, and a literal belly laugh. Thanks for that mate.
Once I finish a project that I'm working on I'll watch a lot of your videos and try to apply some new learnings to my old python projects, really informative things you're pushing out
These are excellent (as are ALL of your videos). Thank you! 😺
Super informative, thank you!
Love your videos man! Super helpful towards improving my coding practices
Probably one of the coolest things I ever created that I unfortunately no longer have was a decorator that would turn a function into a tkinter form automatically.
In what way? Like it would create a form for inputting arguments, and displaying function results?
@@LF-Me yeah exactly
Very cool stuff, Thank You!
I like to add a filter for exception types when writing a retry decorator. When fetching some stuff, it might fail due to connection issues or a rate limiting. Then it is fine to retry it. But if you parse or transform the result in the same function, it will fail always if something is different than expected, so usually no need to retry it. And, my favourite case, if you cause a KeyboardInterrupt at the same time, would it retry it as well?
this was reallly helpfull , i was struggling to write this to evevry function i use to measure time or apply retry functionalliy
atexit: Doug Hellmann's book about the Python 3 standard library pages 995-997 mentions three conditions when atexit will not be invoked: 1) the program dies because of a signal, 2) os._exit() is invoked directly, and 3) a fatal error is detected in the interpreter.
I like the sponsor!😂
A fun follow up video would be a brief overview on how to create your own decorators! I've done so, for some client specific code and it's a fun exercise 😁
Excelent content, thanks for sharing it (: For those thinking about counting vowels in a str, the version below has time complexity of O(n) ```python def count_vowels(input_str: str) -> int: vowels = 'aeiouAEIOU' return sum(1 for char in input_str if char in vowels) ```
It's appreciable ❤
You can also use lru_cache instead of cache, it will automatically remove the cache which is not used recently.
What is the name of the VS code theme used by Carberra
Great content. Thanks! 😀
Thank you :)
Amazing🎉
finally a channel that uses a real IDE
Instead of own retry decorator, use backoff. It's also compatible with asyncio. But it's an additional dependency.
What did you use to make "->" appear as actual arrow "→" 11:18 ?
ligatures, fonts in VSCode and PyCharm support them
0:49 Did pycharm create the time import for you automatically? Or was it just a jump-cut? That's really convenient if it's pycharm. I moved from pycharm to vscode when I needed the paid for features. Meh, probably vscode will do the same thing if pycharm does and I'll never bother to set it up.
Yeah it was PyCharm :)
You can enable auto imports in VS Code by clicking the curly braces next to Python in the bottom status bar and enabling import completions in the menu that pops up.
@@rmHawk765 Huh, it works! Hats off, thanks so much!
Can you help me understand how is the @atexit.register functionality different from Context Manager functionality in Python?
Context managers are for cleanly disposing resources like files and database connections when they're no longer needed. This even happens when an exception is thrown in a "with" block. atexit is for global cleanup at the end of the program, which is usually not needed with small scripts.
functilonally atexit is placing your whole program in a context manager and running the supplied function in the `finally` block
The sponsor shout out was the best lol 😂😆😂
Absolutely epic😎
Retry is already done by the requests library. Cache clear was interesting
Shout-out to the funcy library, while we're here!
The connect() function does not return, because of the raise. The correct typing should be -> NoReturn
If the computation of a function is fixed and it will result in the same result everytime, why would I want to use cache and not just store the output in a variable?
Because what you're talking about is a constant, and creating a constant for every single input scenario is just not ideal, and probably not possible due to the infinite amount of possible inputs.
It would be helpful if you showed the decorator code in the video as well in video.
1:37 17| if retries LT 1 or delay LTE 0: 18| raise ValueError('Are you high, mate?') has me ROFL'ing!
So these aren't 5 Python decorators, they're 5 decorators written by your average Python fan.
Cache and atexit are part of the standard library.
These are cool, thanks. Although it is my personal opinion that retry and get_time shouldn't be decorators, you could just call the higher-order function whenever you need it instead of affecting the original function.
Are the two not equivalent? Except the decorator influences all calls to the wrapped function vs changing the call site online influences one. A decorator is just a higher order function?
@@DrGreenGiantThat is exactly what I mean, I just think it's better to keep your functions less coupled and just use the "decorator" as a normal function, so e.g. when you want to test your code that runs 3 times, you can work with the original function that runs once and not the version that runs 3 times or whatever.
@@spaghettiking653 ah I see what you mean, yes. I guess it depends on the use case. I can imagine a worker function that is being sent to a pool, for example, and it would be probably easier to temporarily decorate the worker, than to change the call site. Especially if there is already some higher order stuff going on with partials, for example. But like you say, I can imagine many other cases where it would be much better to wrap the call site rather than the definition. More food for thought, ty!
@@DrGreenGiant Ty yourself, I didn't give much thought to threads or any other use cases like that :)
nice =D
I want pip install idently 😊
Python decorators are a lot less cool if you have to step into while debugging ... ;) I actually now prefer utility-functions with a lambda, or resources.
My favourite is @mark from pytest
Just using memory is not a memory leak
I don't remember anyone stating that :)
4:40
@cache internally builds a mapping (essentially a dict, but a bit fancier) between the inputs and outputs of each of your function calls. Since this creates a reference to those objects, they don't get garbage collected as long as the function is around, which is typically for the lifetime of the program, long after you're done with them. This can be nasty if you @cache an object method, it prevents the object from being garbage collected at all.
Good time stamp, but I said: "can lead to memory leaks".
Your s good as it cones
retrying is a python module which is present already
If you find it remember to share it with the rest of us :)
Tenacity is a Python package that implements a retry decorator
pip install retrying
Hope it helps ;).. love your content! Learned a lot from it. Keep sharing your knowledge!!
Ahaha, I didn't know you meant "retrying" as in that was the module name, thanks for sharing!
A good set, but I was a little disappointed because some things were not called by their proper names: cache(memoization). Also surprised that wraps from functools wasn't mentioned.
1:37 Are you high, mate? this is the kind of stuff I do for side cases in functions I give it a casual error 💀
You don’t count the amount of vowels. You count the number of vowels. For some reason this distinction, which is elementary school grammar, has complete collapsed within the last 2 years. Same from less/fewer.
Thanks for the English lesson :)
You clearly know what he meant
Wow, deprecated and atexit.register ones are really useful Gonna use them in my project, thank you❤
2:43 : wait, didn’t you say at the start of the video that it was sponsored by indently? Then why do you say it isn’t sponsored?🩳