Hi, Having a new thread for my gsoc project idea 2015. Analyzing for more then a month I have decided to work on django best practices updates project. Tim graham and Russels suggestions helped me to have some ideas related to this project. In this thread I hope to have a in depth discussion for the proposal.
*Background:* 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 -- 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 [email protected]. To post to this group, send email to [email protected]. 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/d0e3e2ac-f3a3-4b72-aada-a3e3c76cb400%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
