goldtech wrote:
I would be grateful for support with the code I cited. It's not long
and fairly standard. I'm sure my error(s) would be glaring to more
experienced coders. I appreciated the "heads-up" about other options
but I would be grateful for help getting this code to run. Thanks
For com
On Jul 13, 5:30 pm, Waldemar Osuch <[EMAIL PROTECTED]> wrote:
> On Jul 13, 3:00 pm, goldtech <[EMAIL PROTECTED]> wrote:
>
> > I would be grateful for support with the code I cited. It's not long
> > and fairly standard. I'm sure my error(s) would be glaring to more
> > experienced coders. I appreci
On Jul 13, 3:00 pm, goldtech <[EMAIL PROTECTED]> wrote:
> I would be grateful for support with the code I cited. It's not long
> and fairly standard. I'm sure my error(s) would be glaring to more
> experienced coders. I appreciated the "heads-up" about other options
> but I would be grateful for he
I would be grateful for support with the code I cited. It's not long
and fairly standard. I'm sure my error(s) would be glaring to more
experienced coders. I appreciated the "heads-up" about other options
but I would be grateful for help getting this code to run. Thanks
On Jul 13, 11:47 am, Stef
goldtech wrote:
> My first attempt at SAX, but have an error message I need help with.
Just in case you prefer writing readable code over debugging SAX code into
existence, try lxml.
http://codespeak.net/lxml/
Here is a presentation you might find interesting.
http://codespeak.net/lxml/s5/lxml-
SAX XML Parse Python error message
Hi,
My first attempt at SAX, but have an error message I need help with.
I cite the error message, code, and xml below.
Be grateful if anyone can tell me what the fix is.
Thanks.
>>>
Traceback (most recent call last):
File "C:\Python24\Lib