Repository navigation
Commit 89e519e
committed
Colorize mypy output when run through tox
On Unix-like systems, this approach is currently only sufficient if
the TERM environment variable is set. In practice this means that
if tox is run on CI, color will not be shown. Because GitPython
does not itself use tox on CI, and other (e.g. downstream) projects
may not want color on CI or in other situations where this would be
insufficient, the further step of defining TERM as a workaround is
deliberately omitted.
See aeacb0 in #1859 for what adding TERM would look like. This does
not make any changes to how mypy runs on CI because that change is
already included there.1 parent dcbd5db commit 89e519e
1 file changed
Lines changed: 2 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -28,6 +28,8 @@ commands = ruff format --check . | |||
| 28 | 28 | [testenv:mypy] | |
| 29 | 29 | description = Typecheck with mypy | |
| 30 | 30 | base_python = py{39,310,311,312,38,37} | |
| 31 | + set_env = | ||
| 32 | + MYPY_FORCE_COLOR = 1 | ||
| 31 | 33 | commands = mypy -p git | |
| 32 | 34 | ignore_outcome = true | |
| 33 | 35 | ||
0 commit comments