[XML-SIG] Re: python SAX API

[Lars Marius Garshol]

* Lars Marius Garshol
|
| What mess? Please be specific.

* Juergen Hermann
| 
| Different version of docs in different cvs branches, with different
| implementations of parsers on top of that. It's a little mess, but a
| mess. ;)

If this is the case then it is indeed a mess. But can you be more
specific? You seem to know about specific problems, could you list
them so that we can get them fixed? Or could you at least tell us
where to look, so that we can find them and fix them?
 
* Lars Marius Garshol
|
| We should be very careful not to try to be too smart here; that
| generally leads to much more subtle problems. Can you explain in
| detail what you think the problem is (because I don't know that there
| is one)? Once you've done that we can try to find some solution.
 
* Juergen Hermann
|
| The problem is that we break the rule of least surprise
| constantly. Even I as a developer involved with (but not 100%
| immersed into) the PyXML code was unsure about things are supposed
| to work. Now imagine the poor little XML- newbie developer out
| there...

OK. This is the same thing that Alexandre is talking about. Can you
list the issues you are aware of? Can you point us at what kinds of
things they are? That way we can get started on ironing them out.
 
| Given Alexandre's msg, I vote for "raise better exceptions and give
| driver writers a guide how to do that" regarding the namespace
| problem (so no intelligently fixing things, but intelligently
| reporting things).

What namespace problem? What things? Please be more specific. It's OK
to say that you don't know precisely, but please try to share all the
information you have. We can't fix this without knowing what the
problem is. :-)

| Also, we need SAX unit tests that check on things like "None
| returned for empty namespace" and things like that.

I agree completely. This is what I was thinking of when I wrote about
automated testing in the task list.

--Lars M.