Repository navigation
(🐞) Invalid per-module options in inline configuration are silently ignored #12342
Description
# mypy: disable-error-code=name-defined python-verion="3.6"
a # error: Name "a" is not defined [name-defined]
But if I include it in the config file it gives a warning:
[[tool.mypy.overrides]]
module = ["test"]
disable_error_code = "name-defined"
python_verion="3.6"> mypy test.py
pyproject.toml: [module = "test"]: Per-module sections should only specify per-module flags (disable_error_code, python_version)
test.py:3:1: error: Name "a" is not defined [name-defined]
Found 1 error in 1 file (checked 1 source file)
This is inconsistent with having a invalid option inline:
# mypy: AMONGUS> mypy test.py
test.py:1:1: error: Unrecognized option: amongus = True [misc]
Found 1 error in 1 file (checked 1 source file)
Activity
[-](🐞) `disable-error-code` doesn't work in inline configuration[/-][+](🐞) Invalid per-module options in inline configuration are silently ignored[/+]wyattscarpenter commentedon May 11, 2025
This is half-fixed by now, in that
gets
Note that there is no error for line 3, even though it doesn't work!
# mypy: disable_error_code=name-definedwill actually disable that error code.wyattscarpenter commentedon May 12, 2025
Oh, looks like the new incorrect behavior is actually much simpler than I thought
works. (no output)
doesn't. (output:
)
wyattscarpenter commentedon May 12, 2025
This github issue was unrelated issue to what I discovered, and this can be closed as complete, as python_version now gets an Unrecognized option error when used per-module.
Fix a bug where inline configurations of error codes would lose their…