#36913: Optimise ChoiceField / MultipleChoiceField handling of duplicate
submissions
-------------------------------------+-------------------------------------
Reporter: Jake Howard | Owner: Sarah
Type: | Boyce
Cleanup/optimization | Status: assigned
Component: Forms | Version: 6.0
Severity: Normal | 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 Natalia Bidart):
Replying to [comment:3 Abhimanyu Singh Negi]:
> I’d like to work on this issue.
>
> From what I understand the slowdown happens because duplicate submitted
values are validated again and again. I’m thinking of validating only the
unique values internally while keeping the original list unchanged so
behaviour stays the same. I’ll add some tests too to make sure duplicates
and invalid values are still handled correctly.
>
> If this sounds reasonable and no one is working on this, i would like to
assign the issue to myself.
This ticket has been assigned already and has been reserved to evaluate
under the Djangonaut Space umbrella. Sorry!
--
Ticket URL: <https://code.djangoproject.com/ticket/36913#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 visit
https://groups.google.com/d/msgid/django-updates/0107019c4e9f5630-96b09d4b-ab64-4e91-b7fd-88d7432fcaad-000000%40eu-central-1.amazonses.com.
