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 are different, why do we import View from django.views.generic? To help developers better avoid confusion and better separate the concepts, I would like to change the import of the View class. Ideally: from django.views import View I would furthermore like to move View from the generic directory into it's own module. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ffad765a-0803-47c1-8bd0-9bd69fff0835%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
