#28219: Paginator warning about unordered object should include stack trace
--------------------------------+--------------------------------------
Reporter: Denise Mauldin | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Comment (by Simon Charette):
I'm pretty sure this is caused by your `Order` model's queryset not being
ordered but it's hard to tell without your model and DRF view definitions.
In all cases there's not Django can do to solve your specific DRF issue.
It should make sure the queryset passed to paginator is ordered and decide
what to do from there.
For the record, the `catch_warnings()` method I suggested in my previous
comment about ''rewarning'' won't work as it's not threadsafe.
--
Ticket URL: <https://code.djangoproject.com/ticket/28219#comment:3>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.32460577625393e56099be9ecbc2dab0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
