#23861: IPAddressField removal will break migrations and test suites
-----------------------------+--------------------------------------
Reporter: spookylukey | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Comment (by spookylukey):
If we do go down the route of requiring squashing to deal with this,
perhaps we can have a modified deprecation policy for fields, so that we
keep stubs for a bit longer and then remove the fields '''all at the same
time'''. This should reduce the number of squashes that are necessary. We
should also document this as best practice for the sake of 3rd party
libraries.
--
Ticket URL: <https://code.djangoproject.com/ticket/23861#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/069.497fa0e9522d3fa510219a910887c270%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
