#17026: Message storage backends section missing "just use x"
-------------------------------------+-------------------------------------
Reporter: coolRR | Owner: aaugustin
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Documentation | Resolution: fixed
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Aymeric Augustin <aymeric.augustin@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [ce53a1d0bf51f59118569ec81e1a30b013bd352e]:
{{{
#!CommitTicketReference repository=""
revision="ce53a1d0bf51f59118569ec81e1a30b013bd352e"
Clarified the messages documentation.
* Stated upfront that the messages framework is enabled by default.
* Explained why FallbackStorage, despites its unattractive name, is the
default and likely the most efficient message storage class.
Thanks Jeremy Dunck for the review.
Closes #17026 (again).
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/17026#comment:5>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
