How to start python extension automatically in a workspace?
See original GitHub issueHello! I love vscode, and the python extension especially. The new vscode remote extension makes the story even better.
I do find one thing to occassionally be a bit of a minor inconvenience, however:
It doesn’t seem like the python extension starts up in a vscode workspace until I do one of a few things – (open a .py file, run a python - *
command in the Ctrl+Shift+P
command pallete, etc). This means that if I open up a terminal window before I’ve done one of those things, my virtual environment for that workspace won’t be activated.
I would love to be able to specify in a workspace that I want the python extension to automatically boot up with the workspace. I asked @DonJayamanne about this in person early today (by the way, it was really awesome to meet you!) and he recommended I submit an issue.
I think he described creating a minimal extension that requires the python extension, but I’m still not sure how to go about that.
Thanks, and sorry for the wall of text!
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top GitHub Comments
@zdog234 Apologies for the delay, the source and the release of the VSIX can be found here https://github.com/DonJayamanne/vscode-activate-python-extension/releases/tag/0.0.1
Extensions: Instal from VSIX
The Python extension will automatically load everytime.
Note: If you don’t want the python extension to load everytime in some places, then:
Reopening to provide a simple extension sample that’ll auto activate the extension for you, (as promised at PyCon, will provide sample instructions to build it your self)