The Swift tests should be re-factored by adding new class for swift objects.
When you receive a swift object, not just content body considered as an object, the full entity including all entity headers must be considered as part of the object.
The swift object python representation, must consider the header names are "token"s, you cannot store the entity-body in the same naming scope as all headers/attributes, unless you pick a header name, which can't be an entity header.
The class may provide shorthand methods for the X-Object-Meta headers or for other header groups.
Note: The headers are case insensitive. Lower case store is practical, case insensitive lookup should be considered.
The accounts and containers should get similar classes, they might have the same base class.
The object when converted to string , it should contains the entity-body only, but the repr should include all other attributes.
Note: The 'status' is not header, but our http client in several cases represent it in a similar way, try to avoid this blind spot.
Note: One header can occur multiple times in a response (http://stackoverflow.com/questions/4371328/are-duplicate-http-response-headers-acceptable), probably our httplib's responsibility to handle it correctly.
Is this bug still open? I would like to work on it if it is :)