Repository navigation
Support wildcard and array options for python.venvPath setting #24369
Description
Following the trail of this issue: #1019, I'd like to request venvPath to support array of paths and wildcards in them.
My use case touches monorepos and as part of monorepo (poly language repo), each project may have one or even many venvs created. Workaround I'm using for now is creating named venvs in the root, which isn't ideal of course, but seems to be do the trick.
Having an ability to have venvs co located with actual projects will remove this artificial limitation. Thus, expected format would be something as discussed in the ticket attached, where we just rename the venvPath to become venvPaths (plural):
"python.venvPaths": ["${workspaceFolder}/apps/*"],
Arrays might be beneficial in case of more granular separation in repo, like "public-apps", "internal-apps".
Activity
karthiknadig commentedon Oct 31, 2024
artsiommiksiuk We have this setting as
"python.venvFolders": [].you should be able to pass:
Give that a try.
artsiommiksiuk commentedon Nov 4, 2024
Karthik Nadig (@karthiknadig), thanks for the suggestion! It works only for non wildcard paths. E.g. I have several apps in
${workspaceFolder}/appsfolder, therefore I need a way to describe them all once, like with wildcard, instead of${workspaceFolder}/apps/app1,${workspaceFolder}/apps/app2.I think it was also discussed in the ticket I've attached. To sum it up, from both tickets, it would be great to have:
venvFoldersandvenvPath. Looks like venvFolders is already covering cases of venvPath.venvFolders, so we can specify more complex cases like${workspaceFolder}/apps/*.eleanorjboyd commentedon Dec 11, 2024
Thank you for submitting your feature request and everyone who considered it! Unfortunately, this issue did not receive enough votes over the allotted time, and so we are closing the issue. PRs are welcome so you can create a PR that fixes this if you are passionate about getting this feature across the finish line. Thanks!