#23861: IPAddressField removal will break migrations and test suites
-------------------------------+--------------------------------------
Reporter: spookylukey | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | 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 claudep):
It's true that with migrations, we are now setting in stone some old
code/symbols, and we have to take this new paradigm into account.
I'm not happy at all about keeping stubs/old code forever in Django.
Some crazy idea without any proof of concept: Add a new django.legacy
module which contains old code and which dynamically injects compatibility
shims into Django current modules only when migrations are run.
--
Ticket URL: <https://code.djangoproject.com/ticket/23861#comment:1>
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.4b3990bfd4d8d304b5d0d68c49726114%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
