#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 Denise Mauldin):

 Replying to [comment:3 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 much 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.

 Yeah, but when there's 50 `Order` model tests and 2 of them throw this
 error, then it's hard to tell what's causing them when the stacktrace just
 points to paginator.  Someone on SO did suggest that I run the tests on
 verbose mode (-v2), so that did help pinpoint which test was throwing the
 error.  However, it'd be nice if the UnorderedObject warning would have an
 option to throw the full traceback so I could tell that it was line 58 in
 my test_api.py.  Maybe that's not possible?

--
Ticket URL: <https://code.djangoproject.com/ticket/28219#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.d2be61bb8965c390757d51715d522a43%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to