Hi Simon,
It might be of use to you to know that the decorator syntax is actually a
syntactic shortcut for a longer way of writing the same thing.
For instance,
@mydecorator
def foo(a, b):
pass
is identical to
def foo(a, b):
pass
foo = mydecorator(foo)
If you wanted to only apply th
...and it was written by some of the original brains behind Zope. So it has a
lot of experiences learnt from the good and bad things from the Zope world. Eg
if you want to (but you don't have to) you can use ZPT, the ZODB, and ZCML with
Pyramid natively. Conversely you could use Mako, SqlAlchemy
Hi James,
Great to see somebody else interested.
About the date, I was thinking of doing it 2 weeks after the django (soon)
and python meetup ( 18 April) .
First to not clashing with them with date and secondly to be able to talk
with some peoples there who could be interested by pyramid but may
Thanks Nick. I wonder if you see any use or validity in an expanded grammar
allowing class-initialisation within the decorator syntax?
Or as Stestagg suggests, there is no real practical need for it?
> decoratedfoo.orig(1, 2) # run original function
Thanks for highlighting decorato
