#23891: Revise deprecation / removal timeline for IPAddressField
----------------------------------------------+--------------------
Reporter: MarkusH | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer (models, ORM) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
As initially mentioned in #23861, the IPAddressField will be removed in
1.9. Given the current way of squashing migration files, this probably
becomes painful to migrate. A proposal that came up in the linked ticket
is to keep a stub field around for a bit longer (maybe 2.0?) that works
(as a noop) in migrations (prevents import errors) but throws errors if
used outside migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/23891>
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/050.fb6c51d0ed241572732b9443fb6551ba%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
