"bruno at modulix" schrieb 
> 
> [snip]
>
> The use case for @decorator is for wrapping functions
> or method *in the module/class itself*. 
That was the question. What's the use of doing it 
like that in the module *itself* (I mean, you change
directly the original function)?

> It's not for module client code (but this of
> course doesn't prevent client code to dynamically 
> add other wrappers...)
> 
How do the clients it? The "oldfashioned"
deco(doSillyWalk)
way?

Martin




-- 
http://mail.python.org/mailman/listinfo/python-list

Reply via email to