You might want to try json encoding your data if you want to preserve
integers, lists, etc.
On Thu, Jul 19, 2018 at 10:54 PM Collin Anderson
wrote:
> Using your example, the client is sending this string:
>
> ?wordPos=2&wordPos=3
>
> It's not an array like ?wordPos=2,3
>
> On Thu, Jul 19, 2018 a
Using your example, the client is sending this string:
?wordPos=2&wordPos=3
It's not an array like ?wordPos=2,3
On Thu, Jul 19, 2018 at 10:27 PM Zhao Lee wrote:
> I have to confess I don’t know much about web development .
>
> I used to expect QueryDict.get(_key_, _default=None_) to return dat
I have to confess I don’t know much about web development .
I used to expect QueryDict.get(_key_, _default=None_) to return data type that
client side offered, for example , if client side send {'wordPos':(2,3)} , I
expect get('wordPos') to return it, whereas the current behavior is far from
ex
I have a reasonable build definition set up on VSTS here:
https://mattc-demo.visualstudio.com/python-ci-testing/_build/index?&path=\&definitionId=8&_a=completed
In order to test against the different databases, I need to wait for our
containerized builds stuff that's coming out shortly. Other than
On Thursday, July 19, 2018 at 8:52:56 AM UTC+2, Carlton Gibson wrote:
>
> The usual case is to need a single value from the query string, so `[]`
> and `get()` both return scalars.
> `getList()` exists specifically for the case where you do want multiple
> values.
>
I'd like to expand on this,
so maybe we should add to the documentation of
https://docs.djangoproject.com/en/2.0/ref/request-response/#django.http.QueryDict
*If want to get multiple values for the same key, use
QueryDict.getlist(key, default=None) instead of QueryDict.get(key,
default=None)*
add example to
https://docs.d
