Search / Quick Open in Virtual Envs

[DylanYoung]

Allow workbench.action.quickOpen to search virtualenvs when using python (or available libraries more generally)

[DylanYoung]

Note: it's hard to tell whether this an enhancement request or bug report as I can't find any documentation on it.

[brettcannon]

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.

If you want this now you can create the virtual environment locally in your workspace and not give it a hidden name, e.g. naming it venv.

[sbidoul]

Such a feature would be helpful. In general, having an easier access to files in sys.path would help. I would add "Reveal Active File in Side Bar" to Search and Quick Open mentioned in the issue title.

For instance, when debugging with justMyCode=false, having some sort of a way for Reveal Active File in Side Bar to show the directory of files entered into with the debugger would be most useful.

[luabud]

Hi @DylanYoung ! I'm closing this issue because like Brett mentioned, this should work if you don't name the virtual environment with a hidden name.
@sbidoul the same is valid for "Reveal Active File in Side Bar". Can you try this out and tell me if you have any issues? If so we can reopen or just open a new one to investigate 😊.

[DylanYoung]

I just added my venv to my workspace, a little annoying but works. The issue for me isn't a hidden name, but rather keeping my virtual environments together so they can be managed easily. I'm not sure, for example how I would easily switch venvs given your proposed workaround (symlinks I guess...). My workaround suffers from the same defects.

I still think the feature mentioned here would be generally useful, but maybe it warrants separate commands so that the PATH doesn't pollute local searches?

[DylanYoung]

As for @sbidoul's comment, it seems to me that that particular command should work for any file, but I think that's a bug and separate from this feature request.

[sbidoul]

@luabud Adding the venv in the project directory or in the workspace is a workaround indeed. As @DylanYoung mentioned this feature is a nice to have for people who store their venvs in a central location (e.g. using virtualenvwrapper).