The other option is to create your own validate decorator, which is precisely what I have done with tgext.crud. You might have a look at this code example:
http://code.google.com/p/tgtools/source/browse/projects/tgext.crud/trunk/tgext/crud/decorators.py On Apr 7, 9:46 am, Mark Ramm <[email protected]> wrote: > No objection from me. 2.1 lives in hg now, and the dispatch refactor > is something that I want to push forward sooner rather than later, so > it may not be long between 2.0 and 2.1. > > Granting you push access to that repo now. ;) > > On Tue, Apr 7, 2009 at 9:28 AM, Diez B. Roggisch <[email protected]> wrote: > > > > > > > Hi, > > > I just noticed that TG2 lost the capability to pass callables as validators > > to > > the @validate-decorator. > > > This is a major drawback, as it prevents the dynamic selection of forms to > > validate. > > > I guess it's to late for TG2.0, but I'd like to implement the feature for > > TG2.1 if nobody opposes. > > > Diez > > -- > Mark Ramm-Christensen > email: mark at compoundthinking dot com > blog:www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
