🌐
GitHub
github.com › microsoft › pyright › issues › 143
Import could not be resolved · Issue #143 · microsoft/pyright
June 4, 2019 - Could not import 'dotenv' in file '/Users/bfelbo/code/pulse/pulse.py' Looking for typeshed stdlib path Attempting to resolve using root path '/Users/bfelbo/.vscode/extensions/ms-pyright.pyright-1.0.36/typeshed-fallback/stdlib/3.7' Could not find directory '/Users/bfelbo/.vscode/extensions/ms-pyright.pyright-1.0.36/typeshed-fallback/stdlib/3.7/dotenv' Did not find file '/Users/bfelbo/.vscode/extensions/ms-pyright.pyright-1.0.36/typeshed-fallback/stdlib/3.7/dotenv.pyi' or '/Users/bfelbo/.vscode/extensions/ms-pyright.pyright-1.0.36/typeshed-fallback/stdlib/3.7/dotenv.py' Attempting to resolve usi
Author   microsoft
🌐
GitHub
github.com › zed-industries › zed › issues › 8540
Pyright "import ' ' cannot not be resolved" identifying imports inside python packages · Issue #8540 · zed-industries/zed
February 28, 2024 - This correctly works internally when running or using anything from the package. However, pyright throws an issue: import anchor_sdk could not be resolved (reportMissingImports) in the IDE.
Author   zed-industries
🌐
GitHub
github.com › microsoft › pyright › issues › 4039
Import couldn't be resolved when a subdirectory package contains a pyproject.toml file · Issue #4039 · microsoft/pyright
October 12, 2022 - That is, if the package is built using setup.py it's fine, but note that you still can't have pyproject.toml file there even when used with setup.py. Basically, pyright recognise the pyproject.toml inside the foo/bar folder as a module instead of foo/bar/bar, so when it resolves import bar, it's looking at foo/bar and not foo/bar/bar.
Author   microsoft
🌐
GitHub
github.com › microsoft › pyright › issues › 1809
Pyright could not resolve import · Issue #1809 · microsoft/pyright
April 30, 2021 - This happens ever since upgrading to pyright 1.1.136, and happens independent of the import as long as it is an additionally installed import (e.g. standard library works fine). I am unsure of the exact version I came from but I verified version ...
Author   microsoft
🌐
GitHub
github.com › microsoft › pyright › issues › 2257
Import could not be resolved · Issue #2257 · microsoft/pyright
September 2, 2021 - Describe the bug I'm getting an unexpected Import could not be resolved. To Reproduce Create a "project" with the following project tree: ├── pyrightconfig.json └── stuff ├── arch │ └── linux.py │ └── base.py <-- symlink of stuff/common/base.py ├── common │ └── base.py └── lol └── loller.py 4 directories, 4 files
Author   microsoft
🌐
GitHub
github.com › microsoft › pyright › issues › 352
Import could not be resolved when folder matches python module name · Issue #352 · microsoft/pyright
November 23, 2019 - If there's a folder and python module with the same name (obviously not a great idea, but the error didn't say what was going on) then pyright fails to resolve an import of the module.
Author   microsoft
🌐
GitHub
github.com › microsoft › pyright › issues › 57
Import could not be resolved for pip packages and local modules · Issue #57 · microsoft/pyright
April 5, 2019 - Describe the bug When opening a file that is known to work in python, all pip based modules and local (to the project) modules are flagged, e.g.: Import 'boto3' could not be resolved To Reproduce Import a pip based module or local module...
Author   microsoft
🌐
GitHub
github.com › microsoft › pyright › discussions › 8557
[Resolved] Resolve bazel dependencies: Import "..." could not be resolved · microsoft/pyright · Discussion #8557
For example, the name of one of these dependencies is "my_dependency". In the BUILD file, I inject this dependency using "@my_dependency". In the python script I use "import my_dependency", and everything works ok. But, using pyright command line, i've got the error Import "my_dependency" could not be resolved.
Author   microsoft
🌐
GitHub
github.com › microsoft › pylance-release › issues › 5204
Pyright reports import warning "X could not be resolved from source" for pygobject modules while stubs installed · Issue #5204 · microsoft/pylance-release
December 4, 2023 - According to Allow line level suppression of specific errors #196 adding # type: ignore or # pyright: ignore[reportMissingModuleSource] to import lines fixes the issue, this is a solution but this isn't an ideal for me since i have a big amount ...
Author   microsoft
Find elsewhere
🌐
GitHub
github.com › microsoft › pyright › issues › 4340
Pyright cannot resolve 3rd party libraries imports - Neovim · Issue #4340 · microsoft/pyright
December 14, 2022 - I have shown an example image below with numpy.array() [2]. But with other 3rd party libraries, for example, cv2 (OpenCV) I am shown the LSP suggested completion for importing but I do not get LSP completions or definitions when trying to use cv2 functions. [3] Another example is with PyTorch I get import cannot be resolved errors however, I still am able to get LSP suggested completions and definitions for PyTorch functions, example image shown below [4]. bs4 says "Import bs4 could not be resolved from source", however LSP suggested completions and definitions still work.
Author   microsoft
🌐
GitHub
github.com › zed-industries › zed › issues › 19344
`Pyright: Import could not be resolved` with multiple `pyrightconfig.json` and `extraPaths` option · Issue #19344 · zed-industries/zed
October 17, 2024 - area:language serverAn umbrella label for all language serversAn umbrella label for all language serversarea:languagesAn umbrella label for all programming languages syntax behaviorsAn umbrella label for all programming languages syntax behaviorsarea:languages/pythonPython programming language supportPython programming language supportbugDEPRECATED label: use issue type 'Bug' insteadDEPRECATED label: use issue type 'Bug' insteadstaleLabel used by `stale` actionLabel used by `stale` action ... Zed doesn't seem to correctly handle multiple pyrightconfig.jsons with extraPaths option at the moment.
Author   zed-industries
🌐
GitHub
github.com › microsoft › pyright › issues › 9610
Pyright can't resolve same-directory imports when having a `pyproject.toml` and a `.pth` file. · Issue #9610 · microsoft/pyright
December 20, 2024 - /home/rgoya/pyright_test/org/foo.py /home/rgoya/pyright_test/org/foo.py:1:8 - error: Import "bar" could not be resolved (reportMissingImports) 1 error, 0 warnings, 0 informations · If I remove either the pyproject.toml or the pyright_test.pth file, pyright works again.
Author   microsoft
🌐
GitHub
github.com › microsoft › pyright › blob › main › docs › import-resolution.md
pyright/docs/import-resolution.md at main · microsoft/pyright
Import hooks can provide an editable ... installation. However, because resolving module locations using an import hook requires executing Python code, they are not usable by Pyright and other static analysis tools....
Author   microsoft
🌐
GitHub
github.com › neovim › nvim-lspconfig › issues › 1861
lsp server pyright import could not be resolved · Issue #1861 · neovim/nvim-lspconfig
Description I mean that the file account/views/oj.py cannot import files in the directory、options、utils、problem. And,the pyright installed by nvim-lsp-installer and nvim-lsp-config in neovim all config items are default. But when i use v...
Author   neovim
🌐
GitHub
github.com › microsoft › pyright › issues › 272
Can't resolve imports in local files · Issue #272 · microsoft/pyright
October 1, 2019 - Describe the bug Pyright is failing to find local modules that Python successfully imports. To Reproduce Make have a folder structure like so: root code __init__.py main.py mymodule.py pyrightconfig.json Where main.py is: import mymodule...
Author   microsoft
🌐
GitHub
github.com › Microsoft › pyright › issues › 97
VSCode failing to resolve imports with Pipenv · Issue #97 · microsoft/pyright
April 28, 2019 - Describe the bug I have a very simple single-file project that uses Pipenv. This is correctly recognised by VSCode but Pyright is just showing "Import could not be resolved". To Reproduce I have a single .py file built with Python 3.7 an...
Author   microsoft