#29125: BUG: Q object deconstruct is inconsistent when passing multiple kwargs.
     Reporter:  Harro                |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  2.0
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:
     Keywords:  has_test             |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
Changes (by Simon Charette):

 * stage:  Unreviewed => Accepted


 Apart from preserving the `kwargs` nature of some children I'd argue that
 `Q.deconstruct` should also use `django.utils.models.Q` as path instead of
 `django.db.models.query_utils.Q` like we do with
 `django.db.models.fields.*` and should avoid adding `_connector` if it's
 `'AND'` and `_negated` if it's `False` to `kwargs` because these are the
 default values.

Ticket URL: <https://code.djangoproject.com/ticket/29125#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 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 
For more options, visit https://groups.google.com/d/optout.

Reply via email to