Replies: 1 comment 1 reply
-
I figured out a solution:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I wrote a package that I am testing locally, but Pylance has issues scanning its paths.
In folder A, I have the repo of package A which I install to my conda environment using `pip install -e path/to/A
When I create a new project B importing A, I get this error message from Pylance:
However, the code runs fine. The module is properly installed in the environment, so
from a.module1 import foo
works perfectly fine.What are the likely causes of this?
[FYI: I am using the newest conda, newest vscode, python 3.10 on the newest MacOS]
Beta Was this translation helpful? Give feedback.
All reactions