Over the years, as Django has evolved, the idea of what constitutes "best practice" has also evolved. However, some parts of Django haven't kept up with those best practices. For example, contrib apps do not use class based views.
In short, Django has been bad at eating it's own dogfood. The contents of contrib should be audited and updated to make sure it meets current best practices.
Objectives:
* Anallyzing django contrib apps to figure out which needs overhaul
* Introducing Class Based views and class based generic views in the contrib apps where necessary
* Drawing update path with backward compatibility in mind
Apps Need to be reviewd:
admin, auth, content-type, flatpages, gis, sitemaps, sites, staticfiles, syndication
- - - - - - - - - - - - - - - - - - - -
this is incomplete draft
I found the following tickets helpful. Any other related old tickets?
https://code.djangoproject.com/ticket/17209, https://code.djangoproject.com/ticket/17208, https://code.djangoproject.com/ticket/16256