Heejae Chang

so. this and this show that we are not getting `python search path`. ``` [Info - 6:29:26 PM] (19530) Search paths for /Users/tjati/Library/Mobile Documents/com~apple~CloudDocs/Development/mysuperproject [Info - 6:29:26 PM] (19530) /Users/tjati/.vscode/extensions/ms-python.vscode-pylance-2023.1.40/dist/typeshed-fallback/stdlib...

did you make sure you are working with `trusted workspace`?, if you are using `untrusted workspace`, vscode won't give us permission to run any executable, meaning we can't run `python...

hmm.. I assume you checked that `python path` points to the right one and you don't have any custom stuff that re-write python path? this is what we actually run...

hmmm.. now I am not sure why you are not getting any search path..... we might need to give you some debug bits to run to see what output we...

I made a change to Pylance so that we log more on python search path. once you install our next pylance pre-release bit (2023.2.11 - which will be most likely...

let me take a look

related issue - https://github.com/microsoft/pyright/issues/6571

good idea. for now, intension was helping users to create an issue to us (even if it doesn't have much info in it) so we have open channel to communicate...

it is due to us not considering `alias` symbol on `user file`. we probably want to support it when we do `full indexing` mode. related to https://github.com/microsoft/pylance-release/issues/5434

did we drop the idea of supplying textmate rule in pylance rather than using one supplied by vscode?