Skip to content

Pylance is using path to environment folder as interpreter path #20657

Closed

Description

@karrtikr
[Info  - 1:44:07 PM] (21220) Pylance language server 2023.2.10 (pyright 01758105) starting
[Info  - 1:44:07 PM] (21220) Server root directory: /home/username/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist
[Info  - 1:44:07 PM] (21220) Starting service instance "venvtest"
[Info  - 1:44:07 PM] (21220) No configuration file found.
[Info  - 1:44:07 PM] (21220) No pyproject.toml file found.
[Info  - 1:44:07 PM] (21220) Setting pythonPath for service "venvtest": "/home/username/Desktop/Tests/Python/venvtest/.venv"
[Warn  - 1:44:07 PM] (21220) stubPath /home/username/Desktop/Tests/Python/venvtest/typings is not a valid directory.
[Info  - 1:44:07 PM] (21220) Assuming Python platform Linux
[Info  - 1:44:07 PM] (21220) Searching for source files
[Info  - 1:44:07 PM] (21220) Found 1 source file
[Info  - 1:44:07 PM] (21220) Background analysis(1) root directory: /home/username/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist
[Info  - 1:44:07 PM] (21220) Background analysis(1) started

Originally posted by Rafal Zebrowski (@zebra-f) in #20644 (comment)

Activity

  1. added
    bugIssue identified by VS Code Team member as probable bug
    area-intellisenseLSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.
    needs PRReady to be worked on
    on Feb 7, 2023
  2. karrtikr commented on Feb 7, 2023

    @karrtikr
    Author

    me neither, but as I have said, there is a problem- Import "numpy" could not be resolved Pylance...

    Rafal Zebrowski (@zebra-f) You reported here #20644 (comment) you were seeing the above behavior.

    Fix should be out in the pre-release version of the extension in half a hr, use the following to try it out:

    image

    Thanks!

  3. zebra-f commented on Feb 7, 2023

    @zebra-f

    Kartik Raj (@karrtikr)

    Fix should be out in the pre-release version of the extension in half a hr, use the following to try it out:

    From quick test it looks like everything works fine with Pre-Release Version.

  4. locked as resolved and limited conversation to collaborators on Mar 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area-intellisenseLSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.author-verification-requestedIssues potentially verifiable by issue authorbugIssue identified by VS Code Team member as probable bugneeds PRReady to be worked onverifiedVerification succeeded

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions