-
Notifications
You must be signed in to change notification settings - Fork 1.2k
How to start python extension automatically in a workspace? #5553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @zdog234 , will this do that for you? |
@karrtikr Thanks for pointing me to #4765. That would definitely be a major quality-of-life improvement. It seems like it'll help a lot when working on structured projects (packages or applications). And for less-structured projects (like a short-turnaround analytics project), I can always just throw one of those files in as a placeholder (it's always worthwhile to have pylint running, even for quick scripts). |
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) |
@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
The Python extension will automatically load everytime. Note: If you don't want the python extension to load everytime in some places, then:
|
Thanks so much! Also, I love that you put this up as a github repo for posterity :D |
Hello! 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 theCtrl+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!
The text was updated successfully, but these errors were encountered: