Re the original question, storing state on your view as a class is fine, because the class is always instantiated and called once per request, with no shared state ( unless you explicitly make it shared through class attributes ). This has the very happy side effect of making testing a lot easier because if you store the intermediate stages of your view logic as attributes on the view object, you can interrogate the view itself at the end of your tests to make sure it did the right thing.
Iain On Fri, Feb 3, 2012 at 8:12 PM, Mike Orr <[email protected]> wrote: > On Fri, Feb 3, 2012 at 8:03 PM, Blaise Laflamme <[email protected]> > wrote: > > same opinion than Chris > > Renaming pyramid_handlers would raise backward compatibility issues, > and there's already a proliferation of things being renamed and > retired. > > I'm just suggesting a sentence in passing, "Class-based views are > sometimes called 'handlers'", so that users know what that term means > and won't misunderstand it. > > -- > Mike Orr <[email protected]> > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" 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/pylons-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
