Re: not well-formed (invalid token)

Brian:

Well, I'll bite... what is the point of using eXpat to parse the
document (where the whole point of eXpat is to expose the document to
an application) if the document is not exposed to your application??

I suspect you're dealing with some sort of a middle man here... or
else you should be able to see the document yourself.

In any case, the question becomes one of:  who is "reading" your
document and supplying it to eXpat... that entity is the really the
only one that can make sense of the line number and offset
information...

This is the absolute extent of my knowledge and ability to make an
"intelligent guess"...  This mailing list is generally for support of
the C eXpat codebase... and I am not convinced you'll find many people
on this list who know the ins and outs of the Python wrapper/bindings
for eXpat.

Nick


On Wed, Aug 18, 2010 at 2:23 PM, Brian <[email protected]> wrote:
> I'm using expat with python 2.6. =A0It's all layered with xmlrpc. =A0The =
actual xml
> doc is short lived and hidden to me. =A0But I can catch "not well-formed =
(invalid
> token)" errors, the line number, and the offset. =A0Unfortunately, the la=
tter two
> are not terribly useful.
>
> Is there a way to get the actual offending token?

-- =

Nick MacDonald
[email protected]