#35440: Update parse_header_parameters to leverage the parsing logic from
(stdlib)
email Message.
--------------------------------------+------------------------------------
Reporter: Natalia Bidart | Owner: Pravin
Type: Cleanup/optimization | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: wontfix
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 Jacob Walls):
* has_patch: 1 => 0
* resolution: => wontfix
* stage: Ready for checkin => Accepted
* status: assigned => closed
Comment:
If any positive changes happen in `email.Message` (e.g. it becomes faster,
simpler, gets a better DX, or acquires a maintainer), then we could
revisit the question of whether it's worth paying a small performance
penalty for less code to maintain in Django, but until that day comes, I
think "wontfix" is the appropriate resolution.
Really any one of those four things coming to pass would be worth
reopening for.
--
Ticket URL: <https://code.djangoproject.com/ticket/35440#comment:34>
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/0107019d6f04216f-34cff306-bd59-450b-8160-fe0a7576d695-000000%40eu-central-1.amazonses.com.
