Import my own module could not be resolved

Output of :CocCommand pyright.version:

[coc.nvim] coc-pyright 1.1.161 with Pyright 1.1.161

Output of :CocCommand workspace.showOutput Pyright:

Workspace: C:\Users\MyPC Using python from C:\Users\MyPC\AppData\Local\Programs\Python\Python39\python.EXE

[Warn  - 8:19:35 AM] Ignored rootPath C:\Users\MyPC of client "pyright"
[Info  - 8:19:35 AM] Pyright language server 1.1.161 starting
[Info  - 8:19:35 AM] Server root directory: C:\Users\MyPC\AppData\Local\coc\extensions\node_modules\coc-pyright\node_modules\pyright/dist/
[Info  - 8:19:35 AM] No pyproject.toml file found.
[Info  - 8:19:35 AM] Setting pythonPath for service "<default>": "C:\Users\MyPC\AppData\Local\Programs\Python\Python39\python.EXE"
[Warn  - 8:19:35 AM] stubPath typings is not a valid directory.
[Info  - 8:19:35 AM] Assuming Python version 3.9
[Info  - 8:19:35 AM] Assuming Python platform Windows
[Info  - 8:19:35 AM] Searching for source files
[Info  - 8:19:35 AM] No source files found.

Here is my python folder:

However, when I import my module in the same directory:

[fannheyward]

The language server, here is Pyright, needs the workspace root to work, coc will try to detect the root by some patterns like .git, pyproject.toml and b:coc_root_patterns, that’s why you need to open vim in your project root.

[smthomas-sci]

In a slightly different issue, where I have pip installed my own module with pip install -e, the python environment finds it when it runs, but pyright fails on linting. This might have something to do with the fact that in site-packages it includes a redirect to the parent directory (not in the workspace dir, because it doesn’t have to be via a pip install). The solution, which enables the python program to run and pyright to find the module, is to create a symbolic link in the workspace folder with the same name as the module, and point it to the original location… Hopefully saves someone time.

Note: adding a pyrightconfig.json with extraPaths: [‘<path_to_module>’], does not work.