Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit89e519e

Browse files
committed
Colorize mypy output when run through tox
On Unix-like systems, this approach is currently only sufficient ifthe TERM environment variable is set. In practice this means thatif tox is run on CI, color will not be shown. Because GitPythondoes not itself use tox on CI, and other (e.g. downstream) projectsmay not want color on CI or in other situations where this would beinsufficient, the further step of defining TERM as a workaround isdeliberately omitted.See aeacb0 in#1859 for what adding TERM would look like. This doesnot make any changes to how mypy runs on CI because that change isalready included there.
1 parentdcbd5db commit89e519e

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

‎tox.ini

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,8 @@ commands = ruff format --check .
2828
[testenv:mypy]
2929
description = Typecheck with mypy
3030
base_python = py{39,310,311,312,38,37}
31+
set_env =
32+
MYPY_FORCE_COLOR = 1
3133
commands = mypy -p git
3234
ignore_outcome = true
3335

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp