[XML-SIG] Re: saxlib 1.0beta

[Lars Marius Garshol]

Paul Prescod wrote:
> 
> Okay, I'm just going to come out and be a jerk:

Well, this should generate some traffic, if nothing else.

> I only think we should
> continue to add stuff to xmllib if we can justify its superiority over
> xmlproc. [...] and
> then optimize the hell out of a *single* XML processor rather than having
> two in wide usage.

How likely is it that other people than me will work on xmlproc? And how
likely is it that having xmllib around will mean that less resources go
into improving xmlproc? (These questions are not meant rhetorically.)

> I would much rather add an sgmllib-like driver for xmlproc 

SAX, rather, to get access to PyExpat as well.

> For some future Python upgrade, we should also consider deprecating the
> sgmllib interface in favour of the SAX interface for the same reasons that
> we would deprecate a socket interface that was too divergent from that
> used in other languages.

Here we differ: to me, a major part of the point of using Python is that
I can easily do stuff that's impossible/much less convenient in ordinary
languages (Java/C++ etc). I like the *mllib interfaces precisely because
they are divergent.

I know this hurts CORBA/JPython integration, but surely we can have the
best of both worlds?

--Lars M. (who dreams of designing a SAX alternative in Common Lisp, to
           see how nice XML processing _really_ could be)