#25385: Import of Views
--------------------------------------+------------------------
Reporter: jambonrose | Owner: jambonrose
Type: Cleanup/optimization | Status: new
Component: Core (URLs) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/25385>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.c90618f7c0fb9e857d1e22e9f8c6c8a2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
