#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: assigned
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* version: 3.1 => 3.0
* severity: Release blocker => Normal
Comment:
After double-checking, it's a regression introduced in Django 3.0
(fa6076daf460df2c2c5ff9f62862f050bc4427f4) when we backported
8be79984dce7d819879a6e594ca69c5f95a08378. Therefore it doesn't qualify for
a backport.
--
Ticket URL: <https://code.djangoproject.com/ticket/32134#comment:4>
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.5276e5bf6d877e6633d2b18ea9d9adf2%40djangoproject.com.
