Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defining FORCE_COLOR=true makes mypy fail with traceback #14139

Closed
ssbarnea opened this issue Nov 19, 2022 · 0 comments · Fixed by #14140
Closed

Defining FORCE_COLOR=true makes mypy fail with traceback #14139

ssbarnea opened this issue Nov 19, 2022 · 0 comments · Fixed by #14140
Labels
bug mypy got something wrong

Comments

@ssbarnea
Copy link
Contributor

Bug Report

This looks like a recent regression as previous versions did not crash when FORCE_COLOR=true.

To Reproduce

export FORCE_COLOR=true
mypy ...

Expected Behavior

To work.

Actual Behavior

Traceback (most recent call last):
  File "/Users/ssbarnea/.cache/pre-commit/repo79gglgcf/py_env-python3/bin/mypy", line 8, in <module>
    sys.exit(console_entry())
             ^^^^^^^^^^^^^^^
  File "/Users/ssbarnea/.cache/pre-commit/repo79gglgcf/py_env-python3/lib/python3.11/site-packages/mypy/__main__.py", line 15, in console_entry
    main()
  File "mypy/main.py", line 70, in main
  File "mypy/util.py", line 538, in __init__
  File "mypy/util.py", line 523, in should_force_color
ValueError: invalid literal for int() with base 10: 'true'

Your Environment

  • Mypy version used: 0.991
  • Mypy command-line flags: --strict
  • Mypy configuration options from mypy.ini (and other config files):
  • Python version used: 3.10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug mypy got something wrong
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant