#31783: Filtering on a field named `negate` raises a TypeError
-------------------------------------+-------------------------------------
Reporter: Aaron Kirkbride | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* easy: 0 => 1
* stage: Unreviewed => Accepted
Comment:
We should either document this limitation or change `_filter_or_exclude`
and friends signature from `(negate, *args, **kwargs)` to `(negate, args,
kwargs)`.
I think the second approach is favourable as there's not much benefits in
using arguments unpacking in these private methods.
--
Ticket URL: <https://code.djangoproject.com/ticket/31783#comment:1>
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/064.83e01e3604039c99798327b90df28f9c%40djangoproject.com.
