You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My reasoning: Given these legacy args are being deprecated in favour of plugins like this one? And that maybe the change to dmypy (#53) now warrants this?
I'm fairly new to the Python world so I hope this makes some sense 😅
Demo
In defaultSettings.json we can see python.linting.mypyArgs with an arg of --follow-imports=silent
We can see that vscode-mypy now reads this setting
And when it passes the arg to dmypy we get a message to say it's not supported, and we do not get Daemon started
After using the workaround we can see Daemon started and a type error in the console
and in the editor
The text was updated successfully, but these errors were encountered:
I don't think merely not reading the legacy args is the solution here. I'm still encountering this, and I don't have that setting.UPDATE: I think I misunderstood. The default for python.linting.mypyArgs is non-empty and it looks like this fix juuust missed the v2023.2.0 release.
Problem
No mypy type hints 😢
Cause
Seems like the default settings for vscode-python is setting
python.linting.mypyArgs
with an arg of--follow-imports=silent
which is not supported bydmypy
(python/mypy#9475)Workaround
Set
"python.linting.mypyArgs": [],
in user or workspacesettings.json
Potential fix
Would a fix be to just stop reading the legacy args here?
Happy to try a PR if so 😉
My reasoning: Given these legacy args are being deprecated in favour of plugins like this one? And that maybe the change to
dmypy
(#53) now warrants this?I'm fairly new to the Python world so I hope this makes some sense 😅
Demo
In
defaultSettings.json
we can seepython.linting.mypyArgs
with an arg of--follow-imports=silent
We can see that
vscode-mypy
now reads this settingAnd when it passes the arg to
dmypy
we get a message to say it's not supported, and we do not getDaemon started
After using the workaround we can see
Daemon started
and a type error in the consoleand in the editor
The text was updated successfully, but these errors were encountered: