#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 Gordon Wrigley):
It seems weird to me that named tuples would work in latest 2.2 and latest
3.1 but not latest 3.0. That sounds like a regression bug in the 3.0 line.
For me personally it not being backported is somewhat inconvenient. Due to
3rd party lib issues this project can't go straight to 3.1, but I can work
around
the lack of backport by overriding the __new__ methods on the named
tuples.
--
Ticket URL: <https://code.djangoproject.com/ticket/32134#comment:7>
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.c1f235776dc5a0529002f7d6d772b6ff%40djangoproject.com.
