Re: What was the rationale behind ClassBasedView.as_view()

There’s also a summary of the various options that were considered: https://code.djangoproject.com/wiki/ClassBasedViews Yours, Russ Magee %-) On Tue, Mar 14, 2017 at 10:08 AM, Frederik Creemers < frederikcreem...@gmail.com> wrote: > That makes heaps of sense, thanks! > > On Mon, Mar 13, 2017

Re: What was the rationale behind ClassBasedView.as_view()

That makes heaps of sense, thanks! On Mon, Mar 13, 2017 at 10:49 PM Daniel Roseman wrote: > On Monday, 13 March 2017 18:36:46 UTC, Frederik Creemers wrote: > > Django views are just functions that take a request, and possibly some > other args, and return a response. To

Re: What was the rationale behind ClassBasedView.as_view()

On Monday, 13 March 2017 18:36:46 UTC, Frederik Creemers wrote: > > Django views are just functions that take a request, and possibly some > other args, and return a response. To get such a view from a class based > view, you can `as_view()` on it. Why is that? Wouldn't it make the code >

What was the rationale behind ClassBasedView.as_view()

Django views are just functions that take a request, and possibly some other args, and return a response. To get such a view from a class based view, you can `as_view()` on it. Why is that? Wouldn't it make the code neater to just implement `__call__` on the views? What was the reing behind