Remove the `-Werror::PytestUnhandledCoroutineWarning` argument
from `epytest`, since the relevant warning is no longer present
in `>=dev-python/pytest-8.4.0`. The newer versions throw an exception
instead, so we don't need any argument.
We could technically still pass it conditionally to pytest version --
but that breaks dev-python/pytest's test suite on upgrade, and working
around that does not seem worth the effort. In the end, this was a QA
check to catch pathological cases, and it should be sufficient to catch
them with the latest pytest version.
Signed-off-by: Michał Górny <
mgorny@gentoo.org>
---
eclass/python-utils-r1.eclass | 1 -
1 file changed, 1 deletion(-)
diff --git a/eclass/python-utils-r1.eclass b/eclass/python-utils-r1.eclass index 6d008bf63664..be6f13673b39 100644
--- a/eclass/python-utils-r1.eclass
+++ b/eclass/python-utils-r1.eclass
@@ -1337,7 +1337,6 @@ epytest() {
-Wdefault
# however, do error out if the package failed to load
# an appropriate async plugin
- -Werror::pytest.PytestUnhandledCoroutineWarning
# override color output
"--color=${color}"
# count is more precise when we're dealing with a large number
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)