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: CONFIGURATION.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,5 +76,7 @@ This server can be configured using the `workspace/didChangeConfiguration` metho
76
76
|`pylsp.plugins.yapf.enabled`|`boolean`| Enable or disable the plugin. |`true`|
77
77
|`pylsp.rope.extensionModules`|`string`| Builtin and c-extension modules that are allowed to be imported and inspected by rope. |`null`|
78
78
|`pylsp.rope.ropeFolder`|`array` of unique `string` items | The name of the folder in which rope stores project configurations and data. Pass `null` for not using such a folder at all. |`null`|
79
+
|`pylsp.signature.formatter`|`string` (one of: `'black'`, `'ruff'`, `None`) | Formatter to use for reformatting signatures in docstrings. |`"black"`|
80
+
|`pylsp.signature.line_length`|`number`| Maximum line length in signatures. |`88`|
79
81
80
82
This documentation was generated from `pylsp/config/schema.json`. Please do not edit this file directly.
We normally support only the most recently released version with bug fixes, security updates and compatibility improvements.
7
+
8
+
9
+
## Reporting a Vulnerability
10
+
11
+
If you believe you've discovered a security vulnerability in this project, please open a new security advisory with [our GitHub repo's private vulnerability reporting](https://github.com/python-lsp/python-lsp-server/security/advisories/new).
12
+
Please be sure to carefully document the vulnerability, including a summary, describing the impacts, identifying the line(s) of code affected, stating the conditions under which it is exploitable and including a minimal reproducible test case.
13
+
Further information and advice or patches on how to mitigate it is always welcome.
14
+
You can usually expect to hear back within 1 week, at which point we'll inform you of our evaluation of the vulnerability and what steps we plan to take, and will reach out if we need further clarification from you.
15
+
We'll discuss and update the advisory thread, and are happy to update you on its status should you further inquire.
16
+
While this is a volunteer project and we don't have financial compensation to offer, we can certainly publicly thank and credit you for your help if you would like.
0 commit comments