Re: QueryDict and its .dict() method - why does it do that?

@Daniel, oh really that Rails is not Django? Haven't noticed on my years of Python web development. Thanks!

@Masklinn

That input is from jQuery's default serializer. It sends the data with contentType 'application/x-www-form-urlencoded; charset=UTF-8'. I just need to pass a data parameter with my JS Object (JSON) and it does the magic.

I understand I can use .getlist() or any other non-optimal solution. I also understand what's going on about keys here (that's why I asked about laziness nature of QueryDict). But following DRY, KISS and other philosophies, couldn't Django do the same as other frameworks assuming it's widely adopted that way? What is the advantage of doing things so differently about that?

Why should I need to implement a lib that re-iterates over the same string that QueryDict already parses to achieve the result that is expected to everyone that is new to Django?

Anyway, thanks for the clear answer and information. And sorry about any grammar errors, English is not my first language.

On Thursday, March 26, 2015 at 2:52:48 PM UTC-3, Gabriel Pugliese wrote:

This gist is self informative - some information from list is lost: https://gist.github.com/gabrielhpugliese/640b69eefc5b7490a07c

Some of my buddies have pasted Rails(Rack) and PHP conversion right below. Is that something I am missing? Does it have to do with laziness?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/800e3c5b-7f5d-457f-957d-9a23d6f83105%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.