decorator

And here's a more magical version that wraps it with a decorator.

What I really want to know is how a framework such as Flask uses a decorator for the route.

[6] It seems like they love the large icons and the massively huge window decorator title bar padding.

The documentation I found on decorators that take args was very brief.

This article has lots of great advice like "test for py2k not 3k" as well as his metaclass decorator that is a lot nicer than six's.

How is the correct function picked for a particular route that is defined against the decorator?

If you want this behaviour, you should just define a higher order function/decorator, and put your "block" in its own function.

Maybe it's some subtle issue like the title bar background color in the window decorator matching the toolbar and menu bar background color.

One cool feature I particularly like is being able to remove window border decorators.

Am I the only one who thinks it's a massive flaw that decorators that take args and decorators that don't are inherently different?

Sort of related: I heard a story where a decorator would write signs that said "wet pant" instead of "wet paint", because the "wet paint" sign would cause people to touch the paint to see if it was indeed wet.

I find the wildcards most useful when implementing decorators or other cross-cutting metaprogramming features.

But you can't seriously claim to me that you can understand decorator idioms, iterables or list comprehensions without a deep understanding of the language.