#33007: `form_clean()` performance
--------------------------------------+------------------------------------
Reporter: David Smith | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Forms | Version: 3.2
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
--------------------------------------+------------------------------------
Changes (by Simon Charette):
* cc: Simon Charette (added)
Comment:
While this particular commit was made to address a correctness issue the
recent influx in optimization PRs merged in the past weeks made me wonder
if we'd rather invest in having some form of CI to confirm their benefit
in the grand scheme of things.
I greatly appreciate having David run these benchmark from time to time
but it'd be great to back optimization PRs with addition to the
performance suite to make sure we don't trade one improvement for another
over time. It would seem like a reasonable ask given how invested we are
in writing regression tests for all bug fixes and feature additions?
Thoughts? Maybe I should bring that up on the mailing list instead?
--
Ticket URL: <https://code.djangoproject.com/ticket/33007#comment:3>
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/066.32b637a06462f6d663c999decc41ab77%40djangoproject.com.
