Closed mercuree closed 4 years ago
I got this too.
I'll be working on this this weekend. The underlying APIs and testing methods for requests have changed enough that I'm going to drop backwards compat for requests earlier than 2.13 (maybe 2.18.)
You're the best @JordanMilne :)
I also ran into this.
any update here?
dudes?
Should I use it on production?
Hi @marataziat, with all due respect I wouldn't suggest using this on production at this time. (I wouldn't use PyT on production either ;) )
KevinHock ok :3
This should have been fixed by advocate 1.0.0, requests 2.18.0 and above are now supported. As a side note, I agree with @KevinHock. Plain requests with a properly configured egress proxy is far preferable :)
Since requests 2.14.0 advocate is broken. requests updated its internal urllib3 version and this can be the cause of the problem. I get an error which relates to urllib3: