django/tests/fixtures_regress/fixtures/bad_fixture2.xml

<?xml version="1.0" encoding="utf-8"?>
<django-objcts version="1.0">
    <objct pk="2" model="fixtures.article">
        <field type="CharField" name="headline">Poker on TV is great!</field>
        <field type="DateTimeField" name="pub_date">2006-06-16 11:00:00</field>
    </objct>
</django-objcts>
Fixed #4371 -- Improved error checking when loading fixtures. Code now catches explicitly named fixture formats that are not supported (e.g, YAML fixtures if you don't have PyYAML installed), and fixtures that are empty (which can happen due to XML tag errors). Thanks to John Shaffer for the suggestion, and Keith Bussell for his work on the fix. git-svn-id: http://code.djangoproject.com/svn/django/trunk@7595 bcc190cf-cafb-0310-a4f2-bffc1f526a37 2008-06-08 10:21:18 +02:00			`<?xml version="1.0" encoding="utf-8"?>`
			`<django-objcts version="1.0">`
			`<objct pk="2" model="fixtures.article">`
			`<field type="CharField" name="headline">Poker on TV is great!</field>`
			`<field type="DateTimeField" name="pub_date">2006-06-16 11:00:00</field>`
			`</objct>`
			`</django-objcts>`