Posts

Most Python programs still talk to their users through print(). That’s fine until you need a progress bar, a table, syntax-highlighted tracebacks, or just readable output that doesn’t run together into a wall of text. rich replaces print() with something that understands color, layout, and structure, and it does it without asking you to learn a templating language first. What it is Rich is a Python library for rendering formatted text, tables, progress bars, syntax-highlighted code, markdown, and tracebacks to the terminal. It detects what your terminal supports (truecolor, 256-color, or plain) and degrades gracefully, so the same code produces reasonable output whether it’s running in a modern terminal, a CI log, or a dumb pipe. ...

You’ve written with open("file.txt") as f: a thousand times. But what does with actually do? Why does the file close even if an exception is raised inside the block? Once you understand the protocol behind it, you can apply the same pattern to database connections, locks, timers, temporary state changes, or anything with a “setup, then guaranteed teardown” shape. The problem with solves Before context managers, resource cleanup looked like this: ...

If you’ve used Flask, pytest, or Django, you’ve used decorators. @app.route, @pytest.fixture, @login_required: they’re everywhere. But most developers treat them as magic syntax without understanding what’s actually happening. Once you do understand them, you’ll start reaching for decorators in your own code. What a decorator actually is A decorator is just a function that takes a function and returns a function. That’s it. def my_decorator(func): def wrapper(): print("before") func() print("after") return wrapper def say_hello(): print("hello") say_hello = my_decorator(say_hello) say_hello() # before # hello # after The @ syntax is shorthand for exactly that reassignment. This: ...