Michał Górny ad01e9c2a9 Fix tests when NO_COLOR is set in the calling environment ... Add `FORCE_COLOR` and `NO_COLOR` variables to the `isolate()` fixture to ensure that these two variables do not affect internal test output. This fixes the following two test failures when pytest is called with `NO_COLOR` set: ``` FAILED tests/unit/test_exceptions.py::TestDiagnosticPipErrorPresentation_ASCII::test_complete_color - AssertionError: assert '\x1b[1merror...ing harder.\n' == '\x1b[1;31mer...ing harder.\n' FAILED tests/unit/test_exceptions.py::TestDiagnosticPipErrorPresentation_Unicode::test_complete_color - AssertionError: assert '\x1b[1merror...ing harder.\n' == '\x1b[1;31mer...ing harder.\n' ```		2023-11-25 07:40:16 +01:00
..
data	Update test_install_package_that_emits_unicode	2023-03-27 11:55:20 +01:00
functional	Enforce f-strings via Ruff (#12393)	2023-11-07 09:14:56 +00:00
lib	Update and provide fixes for mypy pre-commit (#12389)	2023-11-07 09:39:01 +00:00
unit	Update and provide fixes for mypy pre-commit (#12389)	2023-11-07 09:39:01 +00:00
__init__.py	Port to Python3	2011-03-15 15:49:48 -04:00
conftest.py	Fix tests when NO_COLOR is set in the calling environment	2023-11-25 07:40:16 +01:00
requirements-common_wheels.txt	Manually build package and revert xfail marker	2023-09-13 13:40:35 +08:00
requirements.txt	Keep using old virtualenv for Python < 3.10	2022-10-28 01:51:13 +08:00