On Sep 21, 8:44 am, Donald Stufft <donald.stu...@gmail.com> wrote:
> > The goal is to provide a Mixin for class based views, a decorator for class > based views, a decorator for methods, and a decorator for functions, all from > the same codebase. > > Currently I have the decorator for classes working, and the mixin working. I > have the places where the other 2 will go but from a combination of not being > very good at decorators, and not feeling well I haven't finished it yet. I like the overall direction of this approach (mixin class as the root container of functionality) - but a number of technical issues still need to have a resolution demonstrated (ie the decorating function behavior) One, perhaps pony, of a universal approach, would be to convert the decorator kwargs into class attributes, so that they could be overriden in subclasses of a decorated parent, something easy to do with mixins as the starting point. Also on a somewhat related note, a better option for middleware process_view to interact with class based views -Preston -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
