#37080: Django's own tests should always treat both Django deprecation warnings
as
errors
-------------------------------------+-------------------------------------
Reporter: Mike Edmunds | Owner: Héctor
Type: | Castillo
Cleanup/optimization | Status: closed
Component: Testing framework | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"f8c0a9321f07c4bbb338da59d57c38878c85d1f0" f8c0a93]:
{{{#!CommitTicketReference repository=""
revision="f8c0a9321f07c4bbb338da59d57c38878c85d1f0"
Fixed #37080 -- Filtered by generic deprecation warnings in runtests.py.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/37080#comment:12>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019df4200ee6-6db9747b-ed83-48ee-945f-d945847c5f78-000000%40eu-central-1.amazonses.com.
