Jamie Lennox

Ah, that would make sense. It's kind of a bug, but i'm not sure what the solve is. When you do content=fp.read() requests knows the Content-Length to set in the...

Great. `fileLoader` isn't special at all, it just reads the whole file into memory. As above, unless you're doing streaming requests will always download the entire response into memory in...

This one is going back a fair way in my not very good memory. The commit mentions swiftclient which did/does all manner of appalling things (though i never "broke" the...

I think i understand the gist of the question, but i'm not sure how you think that would look. It'd help to start if i know if you're using unittest...

Sorry this has been so long - i really am stuck here on what the best implementation should be. In general i try and match requests as much as possible,...

Hi, I'm not entirely convinced on this one, just because it's a very edge case. What's not working from a multi-thread perspective? I've not done this, but from a quick...

Fix proposed to branch: master Review: https://review.openstack.org/360300 Launchpad Details: [#LPC](https://bugs.launchpad.net/requests-mock/+bug/1616751/comments/1) OpenStack Infra - 2016-08-25 07:42:07 +0000

It seems like a bug. `last_request` should be the actual request and so should be interpretting the underlying object. Can you write it as a test case?

So i can't reproduce the value not being present. Compared to your test case the qs is a list, because you can specify the same qs multiple times, and it's...

That's interesting, it means requests is parsing qs differently based on the scheme of the URL? It's definitely not something we're handling in requests-mock. `mock://` is in the documentation as...