Changes between Initial Version and Version 1 of DjangoWarts


Ignore:
Timestamp:
10/04/2010 10:57:13 AM (8 years ago)
Author:
Luke Plant
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DjangoWarts

    v1 v1  
     1= Django Warts =
     2
     3Cruft that has accumulated in Django that would be nice to see fixed in Django 2.0
     4
     5This page is for vague or broad ideas, and is in addition to the definite plans on the [http://docs.djangoproject.com/en/dev/internals/deprecation/ deprecation timeline].
     6
     7== Form validation/model forms/model saving ==
     8
     9It is a bit complex at the moment - it would be nice to see an API that wasn't constrained by backwards compatibility like the current one was.
     10
     11== Middleware ==
     12
     13The ordering of a stack of request/view/response/exception middleware is pretty complex.  Why do we actually need all these different types of middleware? We could actually write all the middleware as view decorators - simple callables that take a view function and return a view function (this is proved by the fact that you can convert middleware into decorators).  The middleware stack could become a list of decorators that are globally applied.  This brings up the need for how to handle exceptions to the global list of middleware - and how to handle nicely the case of 'sub-views'.
     14
     15== Ticket 14182 ==
     16
     17The !CsrfViewMiddleware stops per-request upload handlers being added - ticket #14182.  The workaround is ugly.
Back to Top