#20439: Deprecate IPAddressField in favour of GenericIPAddressField
-------------------------------------+-------------------------------------
Reporter: erikr | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Forms | Resolution:
Severity: Normal | Triage Stage:
Keywords: dceu13 | Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by joejasinski):
Hey all, would it be possible to simply keep the old IPAddressField around
as a proxy to GenericIPAddressField? I know it adds a bit of redundancy
to the code, but would be one fewer backward-incompatible change to manage
during upgrades. Additionally, people could continue to use the more
concisely named IPAddressField. Just my thoughts...
--
Ticket URL: <https://code.djangoproject.com/ticket/20439#comment:4>
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/063.d7c1c104ad713ee8d5201ab20106344f%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
