Improve docs to clarify that import heuristics don't work for local imports about pylance-release HOT 6 OPEN

@heejaechang got it.
Perhaps it would be good to specify this lacking feature in the READ.me or the documentation more clearly?

I think the reason why issues on this topic keep appearing this is that users can only find outdated information at stackoverflow or old comments in this repo. Maybe I did not find the right section, but if it was addressed clearly (i.e., directly stating "we do not support user file/local discovery, do this instead") it would do wonders for clarity.

from pylance-release.

it is a dup of #5434

currently it is by design. we don't consider alias (import x or from y import x) in user files (ones you refer as local import) for now due to perf issue. (unlike installed packages that dont change once installed, these local imports, we need to repeatedly re-index all dependent files as user change a file)

we are planning to add full mode for people who wants it (it is opt in since most of people don't want to pay that perf hit) but no specific ETA yet.

from pylance-release.

@irm-codebase it looks like I misunderstood your issue. so you are asking about unresolve import not add import code action?

from pylance-release.

Correct. Here, parse_lombadi is on the same directory as the script calling it.

from pylance-release.

I tried your scenario on both windows, WSL, 'Linux` and all worked for me. I guess we need to improve our logging to see what is going on.

from pylance-release.

I added new logging for this case. it will be included in our next pre-release. we probably need that log (unless we can repro it) to figure out what is going on.

from pylance-release.