Hello community, here is the log from the commit of package python-lxml for openSUSE:Factory checked in at 2019-12-07 15:21:57 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-lxml (Old) and /work/SRC/openSUSE:Factory/.python-lxml.new.4691 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-lxml" Sat Dec 7 15:21:57 2019 rev:76 rq:749144 version:4.4.1 Changes: -------- --- /work/SRC/openSUSE:Factory/python-lxml/python-lxml.changes 2019-09-23 12:08:01.589899266 +0200 +++ /work/SRC/openSUSE:Factory/.python-lxml.new.4691/python-lxml.changes 2019-12-07 15:23:17.135729665 +0100 @@ -1,0 +2,5 @@ +Sun Nov 17 14:25:04 UTC 2019 - Dominique Leuenberger <[email protected]> + +- Add lxml-libxml-2.9.10.patch: Fix build against libxml 2.9.10. + +------------------------------------------------------------------- New: ---- lxml-libxml-2.9.10.patch ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-lxml.spec ++++++ --- /var/tmp/diff_new_pack.GLtBzP/_old 2019-12-07 15:23:17.575729604 +0100 +++ /var/tmp/diff_new_pack.GLtBzP/_new 2019-12-07 15:23:17.575729604 +0100 @@ -1,7 +1,7 @@ # # spec file for package python-lxml # -# Copyright (c) 2019 SUSE LINUX GmbH, Nuernberg, Germany. +# Copyright (c) 2019 SUSE LLC. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -26,6 +26,8 @@ URL: https://lxml.de/ Source0: https://files.pythonhosted.org/packages/source/l/lxml/lxml-%{version}.tar.gz Source1: https://lxml.de/lxmldoc-%{version}.pdf +# PATCH-FIX-UPSTREAM lxml-libxml-2.9.10.patch [email protected] -- Fix build against libxml 2.9.10 +Patch0: lxml-libxml-2.9.10.patch BuildRequires: %{python_module Cython >= 0.29.7} BuildRequires: %{python_module cssselect >= 0.9.1} BuildRequires: %{python_module setuptools >= 18.0.1} @@ -71,6 +73,7 @@ %prep %setup -q -n lxml-%{version} +%patch0 -p1 cp %{SOURCE1} . # remove generated files ++++++ lxml-libxml-2.9.10.patch ++++++ >From a2551ed1cb862b2113dc13ca6d057208fe02c31e Mon Sep 17 00:00:00 2001 From: Stefan Behnel <[email protected]> Date: Fri, 1 Nov 2019 08:47:16 +0100 Subject: [PATCH] Adapt doctest to libxml2 2.9.10. --- doc/api.txt | 19 +++++-------------- 1 file changed, 5 insertions(+), 14 deletions(-) diff --git a/doc/api.txt b/doc/api.txt index 9e86d182d..ed8db6ddb 100644 --- a/doc/api.txt +++ b/doc/api.txt @@ -323,9 +323,8 @@ error level: .. sourcecode:: pycon >>> log = e.error_log.filter_from_level(etree.ErrorLevels.FATAL) - >>> print(log) + >>> print(log[0]) <string>:4:8:FATAL:PARSER:ERR_TAG_NAME_MISMATCH: Opening and ending tag mismatch: a line 3 and root - <string>:5:1:FATAL:PARSER:ERR_TAG_NOT_FINISHED: Premature end of data in tag root line 2 This might look a little cryptic at first, but it is the information that libxml2 gives you. At least the message at the end should give you a hint @@ -345,18 +344,10 @@ like this: >>> print(entry.filename) <string> -There is also a convenience attribute ``last_error`` that returns the last -error or fatal error that occurred: - -.. sourcecode:: pycon - - >>> entry = e.error_log.last_error - >>> print(entry.domain_name) - PARSER - >>> print(entry.type_name) - ERR_TAG_NOT_FINISHED - >>> print(entry.filename) - <string> +There is also a convenience attribute ``error_log.last_error`` that returns the +last error or fatal error that occurred, so that it's easy to test if there was +an error at all. Note, however, that there might have been more than one error, +and the first error that occurred might be more relevant in some cases. Error logging
