Force pytest color output on or off based on the presence and value
of NOCOLOR envvar. This fixes inconsistent use of colors that largely
depended on upstream pytest settings.
Signed-off-by: Michał Górny <
mgorny@gentoo.org>
---
eclass/python-utils-r1.eclass | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/eclass/python-utils-r1.eclass b/eclass/python-utils-r1.eclass index 22e00c56815d..225f781cc31f 100644
--- a/eclass/python-utils-r1.eclass
+++ b/eclass/python-utils-r1.eclass
@@ -1291,6 +1291,16 @@ epytest() {
_python_check_EPYTHON
+ local color
+ case ${NOCOLOR} in
+ true|yes)
+ color=no
+ ;;
+ *)
+ color=yes
+ ;;
+ esac
+
local args=(
# verbose progress reporting and tracebacks
-vv
@@ -1302,6 +1312,8 @@ epytest() {
# override filterwarnings=error, we do not really want -Werror
# for end users, as it tends to fail on new warnings from deps
-Wdefault
+ # override color output
+ "--color=${color}"
)
local x
for x in "${EPYTEST_DESELECT[@]}"; do
--
2.34.1
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)