Hi, Bob Kline schrieb am 02.05.21 um 18:56: > The bug I'm asking about in this forum is the second bug, which is > producing an incorrect error message, pretending that the value being > submitted for testing was "Processing complete" (without a newline > character) when the value being tested was actually > "Processing\ncomplete" (with a newline character). The confusion this > misleading error message introduced made it much more difficult than > it should have been to track down and identify the first bug.
It might be that there is some form of space normalisation going on here. In any case, it's not lxml that comes up with this message but libxml2. (In which case this is the wrong place to report this.) You can check whether the "xmllint" tool (that comes with libxml2 as a frontend) shows the same behaviour when you run its XML-Schema validation. Note that lxml probably uses the latest libxml2 on your side (the wheels include it), which may not be same as the library version installed on your system. Stefan _______________________________________________ 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]
