Support symbolic link for `python.venvPath`

[anemele]

Similiar with issue #24369, I have a list of venvs managed by tool uv, they are placed in my home subdir .pyenvs, with a structure like

~/.pyenvs
 ├─env-a
 │  └─.venv
 │      ├─...
 │       ...
 ├─env-b
 │  └─.venv
 │      ├─...
    ......

Setting "python.venvPath": "~/.pyenvs/*" would work if wildcards are supported.

Then I tried to make symbolic link for these venvs, but failed. Symbolic link is not recognized as a venv.

[github-actions]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[eabase]

I have a similar structure when using venvlink and keeping all venv's under C:\venvs\.

# tree -C -L 2 "C:\venvs\"

C:\venvs\
├── geomag
│   ├── Include
│   ├── Lib
│   ├── Scripts
│   ├── pyvenv.cfg
│   └── share
├── myven
│   ├── Include
│   ├── Lib
│   ├── Scripts
│   └── pyvenv.cfg
...

[eabase]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

This is dumb. Nobody is gonna find this issue, that essentially everyone using uv, or venvlink would (or will) have.

[eleanorjboyd]

we now support symlinks on search. let me know if you do not see this working for you!

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!