incubator-libcloud mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Querna (JIRA)" <j...@apache.org>
Subject [libcloud] [jira] Commented: (LIBCLOUD-1) Errors in XML serialization
Date Thu, 11 Feb 2010 01:08:29 GMT

    [ https://issues.apache.org/jira/browse/LIBCLOUD-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832340#action_12832340
] 

Paul Querna commented on LIBCLOUD-1:
------------------------------------

is there anything we want to do here?

I kinda think the LIBCLOUD_DEBUG env variable has replaced the need to debug in element tree
most of the time.

> Errors in XML serialization
> ---------------------------
>
>                 Key: LIBCLOUD-1
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-1
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jeremy Orem
>
> From http://github.com/cloudkick/libcloud/issues#issue/13:
> Errors in the system can turn into XML serialization errors. The one I'm encountering
now (which I haven't quite tracked down) is a name attribute with a value of None. ET constructs
the nodes fine, but when you call ET.tostring() it gives a nasty exception, like:
> ...
>   File "/usr/lib/python2.5/xml/etree/ElementTree.py", line 777, in _raise_serialization_error
>     "cannot serialize %r (type %s)" % (text, type(text).__name__)
> TypeError: cannot serialize None (type NoneType)
> That's not very helpful. Guarding ET.tostring with some debugging code for exceptions
would be handy.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message