#23891: Revise deprecation / removal timeline for IPAddressField
-------------------------------------+-------------------------------------
Reporter: MarkusH | Owner: timgraham
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
Actually, it seems rather difficult to backport this to 1.7 and keep the
test suite output free of these warnings because `call_command()` executes
system checks (changed in master in
685edab9da89b54e3e0e7bbc1c9f8b33d3f45969). Since
`PendingDeprecatingWarning` is silent by default, I think we should just
live with the status quo there. However, if someone wants to attempt the
backport, I'll happily commit it.
--
Ticket URL: <https://code.djangoproject.com/ticket/23891#comment:8>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.ccddffd32112a53a791ebea0c4730d0c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
