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 damien
Recipients ajaksu2, akuchling, damien, exarkun, loewis, pboddie, vdupras
Date 2009-02-04.01:06:11
SpamBayes Score 1.1611914e-08
Marked as misclassified No
Message-id <1233709573.36.0.0388264885616.issue2124@psf.upfronthosting.co.za>
In-reply-to
Content
On Feb 3, 2009, at 3:12 PM, Martin v. Löwis wrote:
> This is DOM parsing, not SAX parsing.

1) The title of this ticket begins with "xml.sax and xml.dom...".
2) I am creating a SAX parser and passing it to xml.dom, which uses it.

> So break layers of abstraction, then. Or else, use dom.expatbuilder,
> and ignore SAX/pulldom for DOM parsing.

Is that really the answer?

Read the source code to xml.dom.*, and write hacks based on what I find 
there?  Note also that xml.dom.expatbuilder does not appear to be an 
external API--there is no mention of it in the documentation for 
xml.dom.*.

> This tracker is really not the place to ask questions; use python-list
> for that.

That was a rhetorical question.

The answer is, as best I can tell, "You can't do that."
History
Date User Action Args
2009-02-04 01:06:14damiensetrecipients: + damien, loewis, akuchling, pboddie, exarkun, ajaksu2, vdupras
2009-02-04 01:06:13damiensetmessageid: <1233709573.36.0.0388264885616.issue2124@psf.upfronthosting.co.za>
2009-02-04 01:06:12damienlinkissue2124 messages
2009-02-04 01:06:11damiencreate