Hmmm...reading further, this probably isn't a good fit, except maybe for prototyping.
apparently it uses eval() internally and imposes a fairly large performance penalty sure does make decorators look nice though. Kevin Horn On Fri, Feb 15, 2008 at 12:59 PM, Kevin H <[EMAIL PROTECTED]> wrote: > > While reading up on decorators today, I came across the "decorator" > module, documented here: > http://www.phyast.pitt.edu/~micheles/python/documentation.html<http://www.phyast.pitt.edu/%7Emicheles/python/documentation.html> > > It's basically a toolkit to make creating decorators easier, and to > make return undecorated function signatures, etc. > > Since one of the issues that has frequently come up in TG is the > complexity of the various decorators, and since TG uses a lot of > decorators, and since the plan at the moment appears to be dropping > Python 2.3 support in TG1.1, I wondered whether there might be some > benefit in using this module to simplify decorators a bit. > > Of course, I'm not really familiar with the module, so I thought I'd > ask the list: > > Has anyone out there used the "decorator" module? > What were the results? > Anyone interested in exploring this? > > Kevin Horn > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
