#23892: Make deconstructible classes forwards compatible
--------------------------------------+-----------------
     Reporter:  MarkusH               |      Owner:
         Type:  Cleanup/optimization  |     Status:  new
    Component:  Migrations            |    Version:  1.7
     Severity:  Normal                |   Keywords:
 Triage Stage:  Unreviewed            |  Has patch:  0
Easy pickings:  0                     |      UI/UX:  0
--------------------------------------+-----------------
 The migration operations don't accept any additional arguments (neither
 `*args` nor `**kwargs`). This will lead to problems in older (>=1.7)
 Django versions if the the migration files for 3rd party apps have been
 created with newer Django versions in case the new operations have a
 different constructor signature. Thus `**kwargs` should be added to all
 operation signatures.

 See the discussion on django-developers for details:
 https://groups.google.com/forum/#!topic/django-developers/nWHVaG6gK0Y

--
Ticket URL: <https://code.djangoproject.com/ticket/23892>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.29c429c9041265566a71bf1930eb8e41%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to