On 2013-10-16 11:10, Javier Guerra Giraldez wrote: > On Wed, Oct 16, 2013 at 10:14 AM, Shai Berger <[email protected]> > wrote: > > However, it does so by blurring the distinction between GET and > > POST parameters, which like other people here, I find > > disturbing. > > care to elaborate about that distinction? both are user-provided > parameters included in the request. the only difference i see is > about encoding.
Because they're sent different ways. POST variables in the request body, and GET parameters are in the URL. But it's possible that a parameter is provided via *both*, and (as Alex notes) the first question in such a case is "where does it look first?" I'm +1 on the eventual removal, possibly with a footnoted function that lets you request the fallback easily if needed. It's a one-liner as Marc details: request.GET.get(key, request.POST.get(key)) or request.POST.get(key, request.GET.get(key)) depending on the priority you want. -tkc -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20131016112949.68b9d342%40bigbox.christie.dr. For more options, visit https://groups.google.com/groups/opt_out.
