[Feature request] Disable automatically making the root folder a Python project

[renan-r-santos]

I have the example below with two folders each having a different uv environment, and the parent folder just as a container.
My local settings.json has this:

    "python-envs.pythonProjects": [
        {
            "path": "project_A",
            "envManager": "ms-python.python:venv",
            "packageManager": "ms-python.python:pip"
        },
        {
            "path": "project_B",
            "envManager": "ms-python.python:venv",
            "packageManager": "ms-python.python:pip"
        }
    ],

Could we have a way to disable automatically making the root folder a Python project?

uv_projects.zip

[eleanorjboyd]

@cwebster-99 and @karthiknadig curious your thoughts here

[FIGIO55]

I'm also interested in this, since from what I can see, the interpreter selected for the root "project" seems to be overriding the interpreter selection for the currently open file.

I have project with a very similar structure as the stated example, with a root that contains many folders that are mini python projects and, when I change files across those mini projects, I can see the virtual environment changing in the bottom right corner, but the interpreter being actually used ends up being the root's one, despite the apparently correct selection, causing vscode to complain about missing packages and so on.

[eleanorjboyd]

Hi @FIGIO55 - thanks for your input here. What you said with "I can see the virtual environment changing in the bottom right corner, but the interpreter being actually used ends up being the root's one"- is a bug. The environment shown in the status bar should be used for execution etc when running. Could you file an issue with the details here (like logging and a recording) so I can take a closer look at this and help figure out the issue?

[eleanorjboyd]

@renan-r-santos still giving this one some thought. I understand your point and want to make sure the "project" default experience works for the most number of people. Lets keep this open and the discussion going as we collect some other env manager perspectives.

[github-actions]

Thanks for the feature request! We are going to give the community time to consider this and add their input!

[FIGIO55]

Hi @eleanorjboyd, I see what mean and I filed an issue with a video recording of what I am experiencing, see #836.
As gathering logs I might need an advice on how to do that since I'm not that familiar in debugging vscode extensions and the output tab for Python Environment did not show anything

[renan-r-santos]

Hi @eleanorjboyd, thanks for letting me know you're still considering this feature request. There's one adjacent problem that I'm not sure should be a separate issue.

In the attached repro, I have one VSCode workspace containing two projects, one in Python and one in Rust. I believe this extension promotes every workspace to a Python project, and it is a bit weird to see any other project there that isn't Python, as you can see in the image.

There's no way to tell the Python Environments extension that a particular workspace in a multi-root workspace setup isn't a Python project. It is a bit related to this issue in the sense that there's no opt-out of being listed as a Python project. For big multi-language monorepos, this list of Python projects can get pretty noisy.

reproducer.zip

[thomaslaich]

I don't quite understand: Isn't this obviously a bug? When i open any python file from a project that is not in the root, the bottom right is showing me a different environment than pylance is using. At the very least, the 2 things should agree on the same environment.

[eleanorjboyd]

Yes, there is an outstanding bug with pylance - microsoft/pylance-release#7443