XML deserialization does not properly handle integers

[dan wendlandt]

The XML deserialization code deserializes everything to a python string, while the JSON code will properly deserialize an integer to a python integer. This leads to inconsistent behavior if API objects contain integers.

Related to bug #818321, but we are using that bug to track the D3 action, which was to remove the code triggering the problem. This bug is to track actual changes to the API code to fix the problem.

[Tyler Smith (tylesmit)]

I'd be more than happy to take this bug if nobody else is clamoring for it. Which of the two routes mentioned in bug #818321 is preferred? Force everything to str, or force all ints to ints and the rest strings?

[dan wendlandt (danwent)]

Awesome Tyler :)

My feeling is that it would be best if the XML deserialization properly handled integers.

[Tyler Smith (tylesmit)]

I think the simple change in the linked branch should do it. I've tested it and get integer values as ints and other values as strings.