#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: Release blocker | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+---------------------
In 21e21c7bc2b8bf7ae127e2aa75048a60d05a6e0f (#23844) we introduced a way
to deterministicly deconstruct migration operations that don't rely on
the argument ordering. However, the migration writer still includes all
arguments of an operations, since it inspects the operation's `__init__()`
function (see
[https://github.com/django/django/blob/12bf42ae0db752bf4a4387d6be7276cd145f59d1/django/db/migrations/writer.py#L51-L52
django/db/migrations/writer.py#L51-L52]).
This behavior makes migrations generated under 1.8 practically unusable on
1.7, even if they don't use managers in migrations. Due to this I classify
this issue as a release blocker.
See also #23892 for a discussion about the forwards / backwards
compatibility of migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/24093>
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/050.d710bce2bfe1cd5cb4aaeef730447b83%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
