| Age | Commit message (Collapse) | Author |
|
Thanks Stavros Korokithakis for the report and Tim Graham for the
review.
|
|
|
|
|
|
@python_2_unicode_compatible.
|
|
|
|
Thanks aklim007 for the suggestion.
|
|
|
|
|
|
|
|
|
|
template objects.
Per deprecation timeline; refs 79deb6a0716e554cac5308e86f5754f19ad436dc.
|
|
|
|
|
|
Per deprecation timeline.
|
|
Per deprecation timeline.
|
|
Per deprecation timeline.
|
|
|
|
optional.
Per deprecation timeline.
|
|
|
|
Per deprecation timeline.
|
|
|
|
|
|
Per deprecation timeline.
|
|
|
|
Per deprecation timeline.
|
|
per deprecation timeline.
|
|
deprecation timeline.
|
|
|
|
deprecation timeline.
|
|
deprecation timeline.
|
|
timeline.
|
|
|
|
Per deprecation timeline.
|
|
timeline.
|
|
|
|
|
|
|
|
|
|
deprecation timeline.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Without an explicit 'level', only messages at WARNING or higher
are handled. This makes the config consistent with the docs
which say, "The django catch-all logger sends all messages at
the INFO level or higher to the console."
|
|
|
|
template tags.
|
|
|