Re: moving the class-based View base class out of django.views.generic?

Very handy +1. -- []'s Paulo Poiati blog.paulopoiati.com On Tue, Sep 22, 2015 at 9:09 PM Russell Keith-Magee wrote: > On Wed, Sep 23, 2015 at 7:06 AM, Josh Smeaton > wrote: > >> Could we have permanent backward-compatible (no deprecation

Re: moving the class-based View base class out of django.views.generic?

On Wed, Sep 23, 2015 at 7:06 AM, Josh Smeaton wrote: >> Could we have permanent backward-compatible (no deprecation timeline) >> shims? I'm -0 if not because it's yet-another thing that everyone needs to >> change when upgrading. >> > +1 That would be my preferred

Re: moving the class-based View base class out of django.views.generic?

> > Could we have permanent backward-compatible (no deprecation timeline) > shims? I'm -0 if not because it's yet-another thing that everyone needs to > change when upgrading. > > +1 -- You received this message because you are subscribed to the Google Groups "Django developers

Re: moving the class-based View base class out of django.views.generic?

Could we have permanent backward-compatible (no deprecation timeline) shims? I'm -0 if not because it's yet-another thing that everyone needs to change when upgrading. On Tue, Sep 22, 2015 at 11:23 AM, Marc Tamlyn wrote: > The idea has been discussed before and was

Re: moving the class-based View base class out of django.views.generic?

The idea has been discussed before and was rejected as needless code churn if I remember correctly. I'm afraid I can't remember when or where this discussion happened, it could have been an in person one at a sprint, I can't immediately find a record on this mailing list. Perhaps the fact it's

Re: moving the class-based View base class out of django.views.generic?

Yup, I think that's a good proposal. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: moving the class-based View base class out of django.views.generic?

Definitely seems like a good idea to me. Even as a frequent CBV user, it always takes me a few seconds to remember to import from generic. John Paulett On Tue, Sep 22, 2015 at 10:41 AM, Tim Graham wrote: > Class-based view users, does this proposal from >

moving the class-based View base class out of django.views.generic?

Class-based view users, does this proposal from https://code.djangoproject.com/ticket/25385 seem like a good one? --- Whenever I talk about class-based views and how their concept is separate from generic views (typically in a class setting), the question I am asked is invariably: if they