#36245: Implement Configurable Content Type Parsing `request.data` to Modernize
the
HTTPRequest
-------------------------------+--------------------------------------
Reporter: Adya | Owner: Adya
Type: New feature | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: duplicate
Keywords: parsing, http | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Adya):
Hey Natalia😊, Thanks for this confirmation.
I get confused because this ticket is not mentioned in the content Idea
description.
https://code.djangoproject.com/wiki/SummerOfCode2025#ConfigurableContentTypeParsing.
But in the description a statement is given:
>The initial phase — targeted for before GSoC — will add request.data and
add support for JSON body handling, but the next phase is to make that
fully pluggable with custom parsers.
What about the initial stage requirements, should I leave it? Will this
problem occur if I did not complete an initial phase statement myself? Or
it would be okay to leave OR #21442 ticket will get counted as initial
phase completion.
Just tell me what I should do now?
--
Ticket URL: <https://code.djangoproject.com/ticket/36245#comment:9>
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/010701958afa09ac-add84995-8aba-4821-9546-579040199e3f-000000%40eu-central-1.amazonses.com.
