This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ocean-city
Recipients amaury.forgeotdarc, andybalaam, ocean-city, realpolitik
Date 2009-10-09.13:00:47
SpamBayes Score 0.00061586045
Marked as misclassified No
Message-id <1255093249.08.0.948991670794.issue6676@psf.upfronthosting.co.za>
In-reply-to
Content
Well, I tried to write test like this.

1. Check if xml.parsers.expat.error is raised.
2. Compare *code* attribute of error object with
xml.parsers.expat.errors.XML_ERROR_FINISHED

But I noticed XML_ERROR_FINISHED is not integer but string. (!)

According to
http://docs.python.org/library/pyexpat.html#expaterror-objects

> ExpatError.code
>
>    Expat’s internal error number for the specific error. This will
>    match one of the constants defined in the errors object from
>    this module.

Is this document bug or implementation bug? Personally, I think string
'parsing finished' as error constant might be useless...
History
Date User Action Args
2009-10-09 13:00:49ocean-citysetrecipients: + ocean-city, amaury.forgeotdarc, andybalaam, realpolitik
2009-10-09 13:00:49ocean-citysetmessageid: <1255093249.08.0.948991670794.issue6676@psf.upfronthosting.co.za>
2009-10-09 13:00:47ocean-citylinkissue6676 messages
2009-10-09 13:00:47ocean-citycreate