Triaged
---
https://code.djangoproject.com/ticket/28917 - Remove paginator's unordered
queryset warning for a .none() queryset (accepted)
https://code.djangoproject.com/ticket/28942 -
ChoiceWidget.option_template_name ignores TEMPLATES DIRS (invalid)
Authored
--
https://github
Now you've said it, having both seems reasonable to me too :)
On 23 December 2017 at 17:42, Shai Berger wrote:
> On Tue, 19 Dec 2017 17:58:35 +
> Adam Johnson wrote:
>
> > Fair. I agree it's more flexible, but it does make "the most common
> > case" of extending the ordering pretty long-win
On Tue, 19 Dec 2017 17:58:35 +
Adam Johnson wrote:
> Fair. I agree it's more flexible, but it does make "the most common
> case" of extending the ordering pretty long-winded:
>
> ordering = qs.get_ordering()
> ordering.append('new_field')
> qs = qs.order_by(*ordering)
>
I don't object to h