-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Disable env activation in PowerShell using command prompt #2892
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
Disable env activation in PowerShell using command prompt #2892
Conversation
news/2 Fixes/2827.md
Outdated
@@ -0,0 +1 @@ | |||
Disable activation of Python Environments in PowerShell by shelling into command prompt and back into PowerShell. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Disable activation of conda environments in PowerShell."
src/client/application/diagnostics/checks/powershellActivationHack.ts
Outdated
Show resolved
Hide resolved
@brettcannon Please re-review |
} | ||
protected async waitForCommandToProcess(shell: TerminalShellType) { | ||
// Give the command some time to complete. | ||
// Its been observed that sending commands too early will strip some text off in VS Terminal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"VS Terminal". You mean "VS Code Terminal"? Probably worth just saying "the terminal" and leave it at that.
For #2732
package.json
are pinned (e.g."1.2.3"
, not"^1.2.3"
for the specified version)package-lock.json
has been regenerated by runningnpm install
(if dependencies have changed)