I don't think I've seen the two-function technique used much, if at all. I'd certainly find it beneficial if more of the pluggables I use took that approach.
I wonder if a central repository of information about best practices would benefit the community? On Oct 15, 3:40 am, bruno desthuilliers <bruno.desthuilli...@gmail.com> wrote: > > Is using RequestContext best practice for apps meant to be pluggable? > > As a general rule, yes. FWIW and while we're at it, another best > practice for pluggable apps would be, whenever possible, to write "two- > folds" views - that is, split the view into two functions, one that do > the job and returns a RequestContext, and the other one - the > "official" view - that calls on the first and takes of the rendering > etc. --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
