#28219: Ease locating origin of queryset paginator warnings
--------------------------------------+------------------------------------
Reporter: Denise Mauldin | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Simon Charette):
> 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?
Did you try running your test suite with `python -W error`? You could use
`warnings.simplefilter` to only error in the `UnorderedObjectListWarning `
case
{{{#!python
import warnings
from django.core.paginator import UnorderedObjectListWarning
warnings.simplefilter('error', UnorderedObjectListWarning)
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28219#comment:6>
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.d22394be62aa227524d1e6c26a1f5938%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
