#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):

 Replying to [comment:10 Natalia Bidart]:
 > Yes, sorry about that, there was a misunderstanding and despite this
 topic was listed in the wiki page, it's not really available for GSoC.
 Some extra data:
 >
 > * the feature already has people working on it (the ones assigned in the
 main ticket)
 > * a few conversations have already occurred in the forum and there was a
 request to write a DEP for this first (see
 https://forum.djangoproject.com/t/request-for-steering-council-vote-on-
 modernising-the-request-object/26816)
 > * the DEP is still in progress at https://github.com/django/deps/pull/88
 >
 > So at this point there is no much to do on this topic except to
 potentially contribute to the DEP to get that finalized and approved.

 Thanks again for this direction, Natalia. There are 5 ideas listed the
 wiki page currently, could you recommend any idea or ticket to work
 (ticket: triage ticket and unassigned).
 Main concern is that the idea or ticket on which I could get a potential
 mentor. In the forum, mentor unavailability is a major concern. So I need
 to choose a idea for which I could get a mentor
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36245#comment:11>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/010701958fd86307-4616ebd4-1211-4ca7-b58f-7d6ddfbf1e10-000000%40eu-central-1.amazonses.com.

Reply via email to