#12327: Internationalization documentation specifies common middleware after
session middleware
------------------------------------+---------------------------------------
Reporter: portante | Owner: nobody
Status: closed | Milestone: 1.2
Component: Documentation | Version: 1.1
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
There's no reason that CommonMiddleware should go first or last. Like most
middlewares, it has no dependencies, which is why the middleware
documentation doesn't mention any. There are only a couple of middlewares
that are order specific - LocaleMiddleware being one of them.
--
Ticket URL: <http://code.djangoproject.com/ticket/12327#comment:1>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
