Fix swiftclient 400 error when OS_AUTH_URL is set.

	Description: The swift command tool will set the auth version
        to 2 if OS_AUTH_URL is set even use -V 1 option to set Version
        to 1.So when use nova/glance client and swift client in the
        same shell, and export environment OS_AUTH_URL, it will lead
        swift client to raise 400 error if swift not use keystone
        for auth.
	Fixes bug 1034158

Change-Id: I8003ff2ad4ac25fd710f87c4dab1507f6040ed3d
Resolves issue with empty os_options for swift-bench & swift-dispersion-report

Fixes Bug 1044204

Change-Id: I5f0863776bc4e2953548bc7a3958141378a032a0
Merge "Resolves issue with empty os_options for swift-bench & swift-dispersion-report"
Merge "	Fix swiftclient 400 error when OS_AUTH_URL is set."
Add OpenStack trove classifier for PyPI

Add trove classifier to have the client listed among the
other OpenStack-related projets on PyPI.

Change-Id: I7b2a9b0e163b79593662bfa799f076f538e3d7ca
Signed-off-by: Doug Hellmann <doug.hellmann@dreamhost.com>
swiftclient Connection : default optional arguments to None

Default the authurl/user/key constructor arguments for the
Connection class to None, as these are not required in the
preauthurl/preauthtoken case

Change-Id: I445a5d365212c365ecc691c0a670a226e2b7954a
Force utf-8 encode of HTTPConnection params

This patch forces swiftclient to encode to utf-8
all url and headers arguments, to avoid the
UnicodeDecodeError which is raised by '\r\n'.join([])
invoked in htplib.py.

Currently the affected projects are Horizon(upload file
with unicode name) and swiftclient CLI('swift post' with
unicode filename as header)

This is also a follow-up of this review:
    https://review.openstack.org/#/c/14216/

I'd still want to hear what the Swift core devs
think of it. Is it better to create a new
AutoEncodingHTTPConnection? Or to handle the connection
creation and make sure there are no unicode and utf-8
string at the same time. If these unicode checks have to
be added in the calling code(Dashboard, CLI), there are
so many places to be added, and also in all new commands
that might be exposed from the API.

Fixes bug 1008940

Change-Id: Ice2aa29024429d3e6f569a88d5cf8b4202537827
Fixes setup compatibility issue on Windows

Fixes Bug #1052161

"python setup.py build" fails on Windows due to a hardcoded shell path:
/bin/sh

setup.py updated using openstack-common/update.py

Change-Id: I763dd5613d91a2523087173b196500648c477fa6
tell nose to explicity test the 'tests' directory

Change-Id: Ib6afa775defc521794da627952edbf69721b0874
fixed inconsistencies in parameter descriptions

Change-Id: I208c7fe97c8ec543b5e1cd230527d3eceb52570f
Merge "Fixes setup compatibility issue on Windows"
Merge "tell nose to explicity test the 'tests' directory"
Remove unused json_request.

- This has been long delegated to python-keystoneclient for auth 2.0.

Change-Id: I92b1fc2db68192cfeefd623c59882f65a4e4405c
Merge "Force utf-8 encode of HTTPConnection params"
Merge "Remove unused json_request."
Stop loss of precision when writing 'x-object-meta-mtime'

str(float) isn't a good way of converting a float to a string with all the precision

Eg

    >>> f = os.path.getmtime("z")
    >>> f
    1347717491.343554
    >>> str(f)
    '1347717491.34'
    >>> "%f" % f
    '1347717491.343554'

Change-Id: I6eb02f7f6730eff814c348d1039eae4606642b52
Adding segment size as another x-object-manifest component

Fix bug 1082930

Change-Id: I2cee91a8f74a3f58379b1b4aefae9401ba5b02c1
Don't add trailing slash to auth URL.

Adding a trailing slash to the authentication URL may interfere with
auth service implementations not using /FOO/ but /FOO as authentication
URL.

OpenStack Object Storage API 1.0 doesn't specify that the auth URL must
end in a slash and swiftclient.client doesn't force it either.

Change-Id: I4e6b6d758d5ccc884e253880513e3d8763ffc2ff
Fixes: bug #1085827
Merge "Adding segment size as another x-object-manifest component"
Don't segment objects smaller than --segment-size

Fix bug 1075184

Change-Id: I369e742ca802744ac20e3575828cfa881018de6d