#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: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Jacob Walls):
* stage: Unreviewed => Accepted
Comment:
Thanks, I can see how this makes testing the assertions themselves more
difficult. (I'll leave Testing Framework as the component in that case.)
> (I think this becomes moot if/when we switch to calendar cycle
releases.)
Can you expand on that part? I'm assuming that part wouldn't change.
--
Ticket URL: <https://code.djangoproject.com/ticket/37080#comment:1>
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/0107019de558f253-0104b1c6-2a30-47c5-a154-55a9ccfb6d12-000000%40eu-central-1.amazonses.com.
