#37080: Django's own tests should always treat both Django deprecation warnings
as
errors
--------------------------------------+------------------------------------
Reporter: Mike Edmunds | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Mike Edmunds):
Welcome Héctor. Please follow
[https://docs.djangoproject.com/en/dev/internals/contributing/writing-
code/ Django's contributor docs] starting with
[https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
/submitting-patches/#claiming-tickets "Claiming" tickets].
--
Ticket URL: <https://code.djangoproject.com/ticket/37080#comment:5>
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/0107019de5d51f66-960f1004-327d-4f9a-b5b0-6b279949ea4a-000000%40eu-central-1.amazonses.com.
