Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package python-httplib2 for openSUSE:Factory
checked in at 2026-10-29 16:11:31
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-httplib2 (Old)
and /work/SRC/openSUSE:Factory/.python-httplib2.new.1255 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-httplib2"
Thu Oct 29 16:11:31 2026 rev:63 rq:1393639 version:0.32.0
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-httplib2/python-httplib2.changes
2026-10-26 10:04:29.310001897 +0100
+++
/work/SRC/openSUSE:Factory/.python-httplib2.new.1255/python-httplib2.changes
2026-10-29 16:13:09.257207067 +0100
@@ -1,0 +2,8 @@
+Wed Oct 28 14:47:55 UTC 2026 - Marius Grossu <[email protected]>
+
+- Add BuildRequires: python-forked for slfo-main
+- Add httplib2-pytest-forked-teardown.patch: append a trailing
+ non-forked test to tests/test_proxy.py to work around
+ pytest-dev/pytest-forked#67.
+
+-------------------------------------------------------------------
New:
----
httplib2-pytest-forked-teardown.patch
----------(New B)----------
New:- Add BuildRequires: python-forked for slfo-main
- Add httplib2-pytest-forked-teardown.patch: append a trailing
non-forked test to tests/test_proxy.py to work around
----------(New E)----------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-httplib2.spec ++++++
--- /var/tmp/diff_new_pack.FlwGjy/_old 2026-10-29 16:13:09.894233783 +0100
+++ /var/tmp/diff_new_pack.FlwGjy/_new 2026-10-29 16:13:09.896233866 +0100
@@ -25,6 +25,11 @@
URL: https://github.com/httplib2/httplib2
Source:
https://files.pythonhosted.org/packages/source/h/httplib2/httplib2-%{version}.tar.gz
Source1:
https://files.pythonhosted.org/packages/source/c/certifi/certifi-2026.10.23.tar.gz
+# PATCH-FIX-OPENSUSE httplib2-pytest-forked-teardown.patch -- work around
pytest-forked/pytest-forked#67:
+# a module whose last executed test is @pytest.mark.forked can leave pytest's
+# internal SetupState stale, making the next module's first test fail setup
+# with "AssertionError: previous item was not torn down properly".
+Patch0: httplib2-pytest-forked-teardown.patch
BuildRequires: %{python_module pip}
BuildRequires: %{python_module setuptools}
BuildRequires: %{python_module wheel}
@@ -38,6 +43,7 @@
BuildRequires: %{python_module cryptography}
BuildRequires: %{python_module pyparsing >= 3.1}
BuildRequires: %{python_module pytest-cov}
+BuildRequires: %{python_module pytest-forked}
BuildRequires: %{python_module pytest-timeout}
BuildRequires: %{python_module pytest}
# /SECTION
++++++ httplib2-pytest-forked-teardown.patch ++++++
--- a/tests/test_proxy.py 2026-06-26 10:11:05.000000000 +0000
+++ b/tests/test_proxy.py 2026-10-28 14:40:16.993506636 +0000
@@ -311,3 +311,22 @@
http = httplib2.Http(ca_certs=tests.CA_CERTS)
response, _ = http.request(uri, "GET")
assert response.status == 200
+
+
+def test_zz_forked_module_teardown_workaround():
+ """No-op test, intentionally not marked @pytest.mark.forked.
+
+ Works around a pytest-forked limitation (upstream issue
+ https://github.com/pytest-dev/pytest-forked/issues/67): forked tests
+ run their whole setup/call/teardown inside a child process, so the
+ *parent* pytest process's internal SetupState is never updated for
+ them. When a forked test is the last test executed in a module, the
+ parent's SetupState can be left stale, and the next module's first
+ test then fails in setup with:
+ AssertionError: previous item was not torn down properly
+
+ Keeping a trailing non-forked test here lets the parent process run a
+ normal setup/teardown cycle and correctly close out this module before
+ pytest moves on to the next one.
+ """
+ pass
