Re: a candidate for a custom decorator?
On 12-Jan-07, at 8:42 AM, Patrick J. Anderson wrote: > @redirect_staff > @redirect_anonymous > def my_view(request): > #view logic and HttpResponse make only one decorator for both options - i think the problem is in chaining the decorators - dont they get nested or something? -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/web/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: a candidate for a custom decorator?
Brian Beck wrote: > I think your problem is the return values. args is a tuple and request > should be there instead. In both of your decorators, return fn(request, > *args, **kwargs) instead of fn(args, kwargs). > > > > > Yes, Brian, that was the problem. Thanks for your help. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: a candidate for a custom decorator?
On 1/12/07, Brian Beck <[EMAIL PROTECTED]> wrote: > > I think your problem is the return values. args is a tuple and request > should be there instead. In both of your decorators, return fn(request, > *args, **kwargs) instead of fn(args, kwargs). > I think you are right. -- I like python! UliPad <>: http://wiki.woodpecker.org.cn/moin/UliPad My Blog: http://www.donews.net/limodou --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: a candidate for a custom decorator?
I think your problem is the return values. args is a tuple and request should be there instead. In both of your decorators, return fn(request, *args, **kwargs) instead of fn(args, kwargs). --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: a candidate for a custom decorator?
I suggest that you print the request, args, and kwargs to see the real arguments. -- I like python! UliPad <>: http://wiki.woodpecker.org.cn/moin/UliPad My Blog: http://www.donews.net/limodou --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
