| Age | Commit message (Collapse) | Author |
|
Follow up to 1b7d524cfa7b7834af26c99407af66be6813938d.
|
|
Follow up to ac59ec8f1a34ea0e82bdb3c77422694e8016e0a7.
|
|
The implementations have unintentionally diverged.
|
|
Thanks Tim Graham for the review.
|
|
The problem:
“3 days ago” should translate to “vor 3 Tagen” in German, while “3 days” translates to “3 Tage”. #21408 describes that django always translated to “Tage”, even when the dative “Tagen” was correct. The same applies to months (“Monate”/“Monaten”) and years (“Jahre”/“Jahren”).
The solution:
Let `timesince` caller provide the string dict to use for the time-related strings.
|
|
* Added logging of 500 responses for instantiated responses.
* Added logging of all 4xx and 5xx responses.
|
|
|
|
|
|
|
|
|
|
django.utils.text.Truncator.
Thanks James Davis for suggesting the fix.
|
|
urlizetrunc template filters.
Thanks Florian Apolloner for assisting with the patch.
|
|
key generation.
|
|
use translations from the generic language variant.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LRU culling turns every read into a kind of write to the cache: cache keys
are moved to the first position in the OrderedDict when they are retrieved.
The RWLock which permitted multiple readers while prioritizing a single
writer is obsolete since all accesses are now writes.
|
|
|
|
continue statements.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SQLite and MySQL.
|
|
|
|
Thanks Andrey Martyanov for the reporti, and Tim Graham for the review.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
arg is raised.
Also removed usage of the problematic pattern elsewhere.
Regression in 6e55e1d88a5c4453e25f0caf7ffb68973de5c0ba.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|