Virtual envs in the workspace are treated as user source

[rchiodo]

I have a workspace folder like so:

• root
  • venv1
  • venv2
  • test.py

When opening the folder, it analyzes the files in the venv that isn't currently selected as if they were user files. I end up with a situation like so:

Exclude paths don't seem to fix the issue either. I tried this:

"python.analysis.exclude": ["venv1", "venv2"]

Additionally our help says all virtual environments are excluded automatically:

[rchiodo]

Turns out I had a workspace settings.json that listed just this:

"python.analysis.exclude": ["test_packages"]

This eliminated the defaults that skip virtual environments. If I remove that exclusion, then the virtual environments are excluded.

[rchiodo]

Perhaps the virtual environments could somehow be a separate setting? Not sure if this really matters anymore.

[rchiodo]

If the default listed out the default options, then this likely wouldn't have been an issue. Something like how the excludes for files does in VS code when you edit it:

    "files.exclude": {
        "**/.git": true,
        "**/.svn": true,
        "**/.hg": true,
        "**/CVS": true,
        "**/.DS_Store": true,
        "**/Thumbs.db": true
    }

[cwebster-99]

@rchiodo I thought this might have been resolved, does this problem still exist?

[rchiodo]

No this still reproduces. It's kind of a problem. I think we should change it to always exclude venv enviroments.