#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 Mariusz Felisiak):
Replying to [comment:9 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.
I'm not sure if I understand, we didn't backport this fix to any stable
branch. Also, using `namedtuple` with the `__range` lookup wasn't tested
or documented.
--
Ticket URL: <https://code.djangoproject.com/ticket/32134#comment:10>
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.53f3ff472d7c355bd4d58fb57a97ba03%40djangoproject.com.
