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
Copy file name to clipboardExpand all lines: README.rst
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,9 @@ Configuration
33
33
``strict`` (default is False) refers to the ``strict`` option of ``mypy``.
34
34
This option often is too strict to be useful.
35
35
36
+
``overrides`` (default is ``[True]``) specifies a list of alternate or supplemental command-line options.
37
+
This modifies the options passed to ``mypy`` or the mypy-specific ones passed to ``dmypy run``. When present, the special boolean member ``True`` is replaced with the command-line options that would've been passed had ``overrides`` not been specified. Later options take precedence, which allows for replacing or negating individual default options (see ``mypy.main:process_options`` and ``mypy --help | grep inverse``).
38
+
36
39
Depending on your editor, the configuration (found in a file called pylsp-mypy.cfg in your workspace or a parent directory) should be roughly like this for a standard configuration:
37
40
38
41
::
@@ -54,6 +57,16 @@ With ``dmypy`` enabled your config should look like this:
54
57
"strict": False
55
58
}
56
59
60
+
With ``overrides`` specified (for example to tell mypy to use a different python than the currently active venv), your config could look like this:
0 commit comments