It seems that the internals of the requests library changed a few
times and broke different things after requests==2.11.1 which is
the version when the tests passed last. Then versions of requests
2.12.0, 2.12.1, 2.12.2, 2.12.3 all broke the tests and finally
version 2.12.4 worked but for the tests to pass we need the changes
from this commit.
Coverage remained the same at 96.396% when pulling 6e509e9f2079c567bca7a1772256c5194c39d021 on fix-legacy-tests into a3308f9e4e488daf7862c0c99b78a08dbf7c6e4f on master.
Coverage remained the same at 96.396% when pulling 6e509e9f2079c567bca7a1772256c5194c39d021 on fix-legacy-tests into a3308f9e4e488daf7862c0c99b78a08dbf7c6e4f on master.
Coverage remained the same at 96.396% when pulling 6e509e9f2079c567bca7a1772256c5194c39d021 on fix-legacy-tests into a3308f9e4e488daf7862c0c99b78a08dbf7c6e4f on master.
Coverage remained the same at 96.396% when pulling 6112458e2de12469b44c28502323fb19363c7871 on fix-legacy-tests into a3308f9e4e488daf7862c0c99b78a08dbf7c6e4f on master.
Coverage remained the same at 96.396% when pulling 97af97e821267963bca6ad8abb89755f5afda16c on fix-legacy-tests into a3308f9e4e488daf7862c0c99b78a08dbf7c6e4f on master.
Coverage remained the same at 96.396% when pulling b2d03d4121c76901f1d9d1bbde26fee071b10cbe on fix-legacy-tests into a3308f9e4e488daf7862c0c99b78a08dbf7c6e4f on master.
It seems that the internals of the requests library changed a few times and broke different things after requests==2.11.1 which is the version when the tests passed last. Then versions of requests 2.12.0, 2.12.1, 2.12.2, 2.12.3 all broke the tests and finally version 2.12.4 worked but for the tests to pass we need the changes from this commit.