#35440: Update parse_header_parameters to leverage the parsing logic from
(stdlib)
email Message.
-------------------------------------+-------------------------------------
Reporter: Natalia Bidart | Owner: Pravin
Type: | Status: assigned
Cleanup/optimization |
Component: HTTP handling | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* cc: Mike Edmunds (added)
* needs_better_patch: 1 => 0
* stage: Accepted => Ready for checkin
Comment:
On second look, we still can't use `email.Message` in the slow path, as
the slow path is still too common (every field in a multipart POST).
The fast paths here are still independently valuable, especially in DRF
use cases where `parse_header_parameters()` is called in nested loops
during content negotiation.
After landing the fast paths, I think we should close this ticket as
`wontfix`. I agree with Mike Edmunds in ticket:36520#comment:25 that any
maintainable/performant solution for complex header parsing is going to
originate with us, not with the standard library.
--
Ticket URL: <https://code.djangoproject.com/ticket/35440#comment:31>
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/0107019d59007899-8c0817a4-6966-4e3b-b53c-544f0e78e8e6-000000%40eu-central-1.amazonses.com.
