#32134: Upgrading 2.2>3.0 causes named tuples used as arguments to __range to
error.
-------------------------------------+-------------------------------------
     Reporter:  Gordon Wrigley       |                    Owner:  Adam
                                     |  (Chainz) Johnson
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  3.0
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Claude Paroz):

 Gordon, you might write to the django-developers mailing list, maybe you
 can get some support to amend the backport policy in case of regressions.
 It also looks weird to me that we backport *regressions* to versions n and
 n-2, but not n-1.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32134#comment:9>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.02a8e1083755a8d078ebaf1aeced027a%40djangoproject.com.

Reply via email to