-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Reactivating Terminal #24699
Comments
Your workaround does technically get the "Reactivating terminals" loop to stop, but it does not solve the problem of the Python extension failing to be used. |
@RMvirtual Please create a new bug and provide details on what is happening. Include logs from Output > Python, and Output > Python Locator. Include your settings as well. |
Same problem, my python extension cannot work
This workaround does technically get the "Reactivating terminals" loop to stop, but it does not solve the problem of the Python extension failing to be used. How to setting python.locator to js? I find it in setting dashboard. Good, setting python.locator to js solve my problem, I can reset my env now. |
Hello can you please elaborate on the "
|
@aantora You can use the settings UI to find that: Click on the link that says "edit in settings.json", paste the above line at the end: As for the |
When activating python extension, you see "Reactivating Terminal" in the status bar, and it does not go away.
Workaround:
settings.json
, and Reload VS Code:Python: Clear cache and reload
.python.locator
tojs
.The text was updated successfully, but these errors were encountered: