#23861: Fields referenced in migrations cannot be (re)moved, even if migrations
have been squashed
---------------------------------+------------------------------------
Reporter: spookylukey | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by timgraham):
In #23891, I've proposed handling the deprecation of `IPAddressField`
using the system check framework. Perhaps we can recommend this solution
for third-party fields as well.
--
Ticket URL: <https://code.djangoproject.com/ticket/23861#comment:13>
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.4994179cb3afa20ef1bc6f814f8a635e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
