#24093: Migration writer includes kwargs for operations even if they don't
occur in
the deconstruct output
----------------------------+------------------------------------
Reporter: MarkusH | Owner: MarkusH
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Changes (by carljm):
* severity: Release blocker => Normal
* stage: Unreviewed => Accepted
Comment:
As I said on #23892, I don't think we should attempt to make migrations
forwards-compatible, and I actually see some advantage to having them fail
fast if you try rather than "maybe work depending which features you use."
So I don't believe this is high priority or should be a release blocker.
However, I do think this is worth fixing, not for forward-compatibility
but just for the sake of cleaner migration files. And if we want it to
"fail fast" when you use newer migrations on older Django, we should do
that in a more explicit way anyway. So I'm +0 on merging this change.
--
Ticket URL: <https://code.djangoproject.com/ticket/24093#comment:2>
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/065.e2a08e95ce9db2985d117f29849cf327%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
