Comments on: Annotations

By: 2.25.2 released - …for the adult in you

2.25.2 released - …for the adult in you — Wed, 22 Oct 2008 17:48:58 +0000

[...] Changed keybindings to be in a single place (Thomas ) (GNOME bug 469361) [...]

By: Thomas Thurman

Thomas Thurman — Mon, 20 Oct 2008 03:20:11 +0000

@Robin: Thank you; I stand corrected.

@Henrique: Thank you. It’s people like you that make it all worthwhile!

By: Henrique Rodrigues

Henrique Rodrigues — Sun, 19 Oct 2008 22:04:17 +0000

This is what I like about Metacity. It may not be full featured, but it does what it’s supposed to do and does it very well, always trying to perfect it’s architecture. When I look at other, more “flashy”, window managers, I think: yes, they’re pretty, but do they have people behind them that think about all the details of a window manager like Metacity’s devs? I really don’t think so. My only hope is that the other window managers drink from Metacity’s cup.

Good job, guys. I really hold Openbox dearly close to my heart, but Metacity takes the gold.

By: Robin

Robin — Sat, 18 Oct 2008 23:00:08 +0000

You seem to have the wrong idea about what Python’s parameter annotations are. Parameter annotations are not meant to replace decorators, they complement them. With parameter annotations it’s possible to add information to single parameters, like a documentation string for example:

def compile(source: “something compilable”,
filename: “where the compilable thing comes from”,
mode: “is this a single statement or a suite?”):
…

Source, file and mode are normal parameters of the function for which the caller has to provide a value, unlike with the ticket example. For that you would use a normal function decorator:

@ticket(177177)
def test_frobulation(): …