#33724: Changing from list to set in `exclude` raises errors, and is not
documented.
-------------------------------------+-------------------------------------
Reporter: אורי | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by אורי):
Hi, just to let you know - if I either convert `exclude` to a set or
convert it to a list, and then add my values, then it works with all
versions of Django. So the problem was just that I assumed it's a list,
instead of converting it to a set or list. Maybe it's better to recommend
it in the documentation - convert `exclude` to a set or list if it's not
`None`.
Commit - https://github.com/speedy-net/speedy-
net/commit/c76c82bc0b40ed06f11a27cd6f0e4deab2a70d47
--
Ticket URL: <https://code.djangoproject.com/ticket/33724#comment:5>
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/01070180dcac2fcc-fbbe8b75-6feb-4915-adf4-ba7eb6d36cf5-000000%40eu-central-1.amazonses.com.
