Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

Commit 8c41e23

Browse files
authored
Update troubleshooting known issues (#1176)
1 parent c889543 commit 8c41e23

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

TROUBLESHOOTING.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,17 +9,13 @@ in [Filing an issue](#filing-an-issue).
99

1010
There are a few known issues in the current version of the language server:
1111

12+
- Import statement handling may be too strict, leading to "unresolved import" messages and the lack of analysis.
13+
- The language server considers the workspace root to be the root of user code imports. For the most part, this can be modified by adding additional folders to the `python.autoComplete.extraPaths` setting, for example, `"python.autoComplete.extraPaths": ["./src"]`, if `src` contains the user code. A `.env` file with `PYTHONPATH` set may also help.
14+
- Editable installs (`pip install -e` or `setup.py develop`) are known not to work with `extraPaths` when the package is installed. (#1139, #1013, #1137, #989, others).
1215
- Not all `__all__` statements can be handled.
1316
- Some modules may have an incorrect list of exported names.
1417
See [#620](https://github.com/Microsoft/python-language-server/issues/620),
1518
[#619](https://github.com/Microsoft/python-language-server/issues/619).
16-
- Inspection of some builds of some compiled libraries (some modules of numpy or pandas) may fail.
17-
- This will prevent the analysis from being completely accurate, but will not otherwise impact the
18-
language server, as the error occurs in another process. A popup may appear in Windows or macOS
19-
when the crash is detected by the operating system.
20-
See [#740](https://github.com/Microsoft/python-language-server/issues/740).
21-
- Analyzing large Conda environments leads to spikes in CPU usage.
22-
- In some cases, CPU usage is as high as 100%. See [#875](https://github.com/Microsoft/python-language-server/issues/875).
2319
- Persistent issues with high memory consumption for users.
2420
- In some contexts, users are experiencing higher than average amounts of memory being consumed. See [#832](https://github.com/Microsoft/python-language-server/issues/832).
2521

0 commit comments

Comments
 (0)