#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.1
(models, ORM) |
Severity: Release blocker | 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):
* needs_better_patch: 0 => 1
* version: 3.0 => 3.1
* severity: Normal => Release blocker
Comment:
It works in Django 3.0, as far as I'm aware it's a regression in Django
3.1, see 8be79984dce7d819879a6e594ca69c5f95a08378.
Marking as "needs improvement" because the patch breaks the original fix,
see #30687.
--
Ticket URL: <https://code.djangoproject.com/ticket/32134#comment:2>
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.2bcf42f26a2aed4b9268815d8015f7eb%40djangoproject.com.
