#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 אורי):
Replying to [comment:1 Mariusz Felisiak]:
> ...
> > What is the best written code to change the line `exclude +=
['username', 'slug']` in my code? Is it exclude `|= set(['username',
'slug'])` or `exclude |= {'username', 'slug'}`? Or should I convert to
list and then back to set?
>
> Personally I would use `exclude |= {'username', 'slug'}` or
> {{{
> exclude.add('username')
> exclude.add('slug')
> }}}
Thank you. Should I assume `exclude` is a set from Django 4.1, or should I
convert it to set? Especially since in Django 4.0 it's a list.
--
Ticket URL: <https://code.djangoproject.com/ticket/33724#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/01070180dbaed7e5-d55bb7e7-7dd8-4797-b51f-b145afb8bd41-000000%40eu-central-1.amazonses.com.
