Note, I also get a similar error for loading JSON:

ValueError: No JSON object could be decoded

On Mar 11, 7:54 pm, Chris <[email protected]> wrote:
> I'm using Django 1.0.2, and I dumped out a sample database as XML
> using dumpdata. When I run my unittests using this XML as a fixture, I
> get the error:
>
> Problem installing fixture '/workspace/project/main/fixtures/
> simple.xml': Traceback (most recent call last):
>   File "/workspace/project/common/zip-packages/django-1.0.2.zip/django/
> core/management/commands/loaddata.py", line 116, in handle
>     for obj in objects:
>   File "/workspace/project/common/zip-packages/django-1.0.2.zip/django/
> core/serializers/xml_serializer.py", line 116, in next
>     for event, node in self.event_stream:
>   File "/usr/lib/python2.5/site-packages/_xmlplus/dom/pulldom.py",
> line 232, in next
>     rc = self.getEvent()
>   File "/usr/lib/python2.5/site-packages/_xmlplus/dom/pulldom.py",
> line 265, in getEvent
>     self.parser.feed(buf)
>   File "/usr/lib/python2.5/site-packages/_xmlplus/sax/expatreader.py",
> line 220, in feed
>     self._err_handler.fatalError(exc)
>   File "/usr/lib/python2.5/site-packages/_xmlplus/sax/handler.py",
> line 38, in fatalError
>     raise exception
> SAXParseException: <unknown>:20:41: unbound prefix
>
> This error seems to be caused by <gd:email> tags, like:
>
>   <property name="email" type="gd:email"><gd:email
> address="[email protected]" /></property>
>
> Why is Django having problems parsing its own XML? Removing the "gd:"
> seems to silence the error, but how can I get Django to output valid
> XML that won't break the unittests?
>
> Regards,
> Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to