Ville Vainio <[EMAIL PROTECTED]> writes:
>> "Ilpo" == Ilpo Nyyssönen writes:
>
> Ilpo> Pickle doesn't have validation. I am not comfortable for
> Ilpo> using it as storage format that should be reliable over
> Ilpo> years when the program evolves. It also doesn't tell me if
>
> Th
"Fredrik Lundh" <[EMAIL PROTECTED]> writes:
> Ilpo Nyyssönen wrote:
>
>> What is the point in doing validation if it isn't done every time? Why
>> wouldn't I do it every time? It isn't that slow thing to do.
>
> DTD validation is useful in two cases:
[...]
I didn't mention DTD validation. Yes, I
> "Ilpo" == Ilpo NyyssÃnen writes:
Ilpo> Pickle doesn't have validation. I am not comfortable for
Ilpo> using it as storage format that should be reliable over
Ilpo> years when the program evolves. It also doesn't tell me if
That's why you should implement xml import/export mecha
no wait, *three* validating parsers/validators for ET
http://online.effbot.org/2005_02_01_archive.htm#elementrxp
http://codespeak.net/lxml/
http://www.leuthe.homepage.t-online.de/minixsv/minixsv_overview.html
parse(os.popen("xmllint --valid %s" % filename))...
I'll come in again.
> > At least the interface looks quite simple and usable. With some
> > validation wrapping over it, it might be ok...
>
> I was going to point you to a validating parser for ET, but the "it might
> be ok" statement is a bit too arrogant for my taste.
I'll point you all to *two* validating parser
Ilpo Nyyssönen wrote:
> What is the point in doing validation if it isn't done every time? Why
> wouldn't I do it every time? It isn't that slow thing to do.
DTD validation is useful in two cases: making sure that data from
a foreign source has the right structure, and making sure that data
you c
