python-swiftclient

History

Timur Alperovich 32f6b3c642 Do not set Content-Type to '' with new requests.

Previously, python-swiftclient worked around a requests issue where
Content-Type could be set to application/x-www-form-urlencoded when
using python3. This issue has been resolved and a fix released in
requests 2.4 (fixed in subsequent releases as well). The patch makes
the workaround conditional on the requests version, so that with
sufficiently new requests libraries, the Content-Type is not set.

For reference, requests 2.4 was released August 29th, 2014. The
specific issue filed in the requests tracker is:
https://github.com/requests/requests/issues/2071.

Related-Change: I035f8b4b9c9ccdc79820b907770a48f86d0343b4
Closes-Bug: #1433767

Change-Id: Ieb2243d2ff5326920a27ce8c3c6f0f5c396701ed

2017-06-13 10:41:01 -07:00

__init__.py

Use "# noqa" instead of "#flake8: noqa"

2016-02-09 23:09:24 +08:00

authv1.py

Add v1password keystoneauth plugin

2016-10-24 01:52:37 +02:00

client.py

Do not set Content-Type to '' with new requests.

2017-06-13 10:41:01 -07:00

command_helpers.py

Add additional headers for HEAD/GET/DELETE requests.