On Nov 26, 2:33 pm, "Wang, Harry" <[EMAIL PROTECTED]> wrote:
> Full Traceback enclosed:
>
> Test Suite Started @ 2007-11-26 11:34:46.617000
> Traceback (most recent call last):
>   File "C:\UDR2\UDRxmlGateway.py", line 370, in <module>
>     ParseAll()
>   File "C:\UDR2\UDRxmlGateway.py", line 286, in ParseAll
>     py_obj = gnosis.xml.objectify.XML_Objectify(InputFile).make_instance()
>   File "C:\python25\Lib\site-packages\gnosis\xml\objectify\_objectify.py", 
> line 160, in make_instance
>     o = self.ParseFile(self._fh)
>   File "C:\python25\Lib\site-packages\gnosis\xml\objectify\_objectify.py", 
> line 190, in ParseFile
>     self._myparser.ParseFile(file)
> xml.parsers.expat.ExpatError: not well-formed (invalid token): line 68, 
> column 0
>
> Harry C. Wang
> Sr. Test Engineer (Automation)
> AOL Mobile
> Phone 206 - 268 - 7502
> temporary e-mail: [EMAIL PROTECTED]
> Personal e-mail: [EMAIL PROTECTED]
>
> ________________________________
>
> From: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED]
> Sent: Mon 11/26/2007 12:19 PM
> To: [EMAIL PROTECTED]
> Subject: Re: gnosis XML objectify
>
> On Nov 26, 1:46 pm, "Wang, Harry" <[EMAIL PROTECTED]> wrote:
>
> > The gnosis xml libs should not be version specific, but when I try to use 
> > Python 2.5, I am getting "not well formed (invalid token)" errors.
>
> > Harry
>
> When does this happen? When you import the module? When you pass it
> some xml? Do you have a full traceback?
>
> Mike
> --http://mail.python.org/mailman/listinfo/python-list

Googling the error seems to indicate that the problem may be an
encoding issue. Check the following threads:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg00787.html
http://article.gmane.org/gmane.comp.python.devel/90093
http://mail.python.org/pipermail/python-list/2007-July/450288.html

Mike
-- 
http://mail.python.org/mailman/listinfo/python-list

Reply via email to