Hi Bob
I'm glad you found a solution for your issue. I got stuck on a validation issue
once which said "'<' expected" and there certainly was one - in the text
editor, but in a binary file editor I could see a couple of non-printable
characters.
It still strikes me as strange that an error message reading " 'a b' is not in
the set {'a b', 'a c'} is somewhat misleading, so I did some debugging and
found that right the way up to the call to vfprintf, the error message contains
the '\n'. I will likely raise something on the libxml2 lists/issue tracker to
see if there is a belief that non-printable characters should be converted when
outputting an error message.
Paul
-----Original Message-----
From: Bob Kline <[email protected]>
Sent: 02 May 2021 20:24
To: Paul Higgs <[email protected]>
Cc: Stefan Behnel <[email protected]>; [email protected]
Subject: Re: [lxml] Re: Tested value modified in validation error message
On Sun, May 2, 2021 at 1:45 PM Paul Higgs <[email protected]> wrote:
>
> I just created the following
> ...
> I will look into the libxml2 to see where the \n is being converted to a
> <space>.
> ....
Actually, your repro case is showing the correct behavior. In other words, the
\n is NOT being converted to a space character. I created a comparable repro
case using lxml.etree, and observed the correct behavior there, as well. So I
dug a little further, and found that the second bug is actually in our own
code. So, I am suitably embarrassed, and I apologize for the wild goose chase.
Thank you both for helping to nudge me back onto the path of truth. :-)
Regards,
Bob
--
Bob Kline
https://www.rksystems.com
mailto:[email protected]
_______________________________________________
lxml - The Python XML Toolkit mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/lxml.python.org/
Member address: [email protected]
