#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"a56586eafeb6d1212bc291d1a2e7d33c87edbc33" a56586ea]:
{{{
#!CommitTicketReference repository=""
revision="a56586eafeb6d1212bc291d1a2e7d33c87edbc33"
Fixed #32134 -- Fixed crash of __range lookup with namedtuple.
Regression in 8be79984dce7d819879a6e594ca69c5f95a08378.
Thanks Gordon Wrigley for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32134#comment:6>
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.2f582b372b905a658b117e90abc8ca66%40djangoproject.com.
