How to enable environment sorting for Select Interpreter?

[cdce8p]

I was wondering how I can enable the newly introduced environment sorting for the Select Interpreter command.

The VS Code changelog mentions that it's enabled by default, but that doesn't seem to be the case: https://code.visualstudio.com/updates/v1_59#_python

I've also tried adding this to the user config:

    "python.experiments.optInto": [
        "pythonSortEnvs",
    ]

Are there any more requirements? I would really like to try it out.

--
VS Code: 1.59.0
Python extension: v2021.8.1102490946

[brettcannon]

You should have by having the 2021.8 release. Can you share a screenshot of your environment picker and explain why you think it isn't working for you?

[cdce8p]

This is how it looks like at the moment (two more pages not shown here). I would have expected venv-310 to be listed first. Followed by venv-39 and venv-38 not shown here. Installs from /usr/local/bin/... and /Library/Frameworks/... should have been at the end.

--
If it's of any help, I'm using macOS Catalina (10.15.7) currently.
Issue is still present with v2021.8.1105858891 released an hour ago.

[luabud]

thanks for the info @cdce8p! Do you mind checking the Python Output channel? You should see an entry there for "pythonSortEnvs" like in the screenshot below:

If you don't, can you open your settings.json (View > Command Palette... and run "Preferences: Open Settings (JSON)") and make sure you don't have an entry with the following:

"python.experiments.optOutFrom": ["All"],

If you do have it, you can just remove that setting, reload the window and then it should work.

[cdce8p]

Thanks @luabud for the response. I indeed had disabled all Python experiments some time ago and seem to have forgotten about it. Don't know if it's possible, but it would have been awesome if VS Code would have detected that these two settings are in conflict to each other.

After checking it out now, I still noticed an issue with the way the environments were sorted. The extension didn't seem to recognize my local venvs. I narrowed the issue a bit and opened #16893

[luabud]

Wow! Thank you very much for digging into it and providing the PR with the fix 🤩
I opened a discussion about the first point you made, to handle the case when both settings are in conflict with each other: #16907