Replies: 2 comments
-
Are you saying the command that VS Code is sending to the terminal isn't working, or is this something you're typing manually? And your example wouldn't work as I believe PowerShell will interpret that as an absolute path on C:, so unless you have a |
Beta Was this translation helpful? Give feedback.
0 replies
-
The problem is solved. Everything is working as it should now, thank you
Вт, 7 февр. 2023 г. в 05:38, Brett Cannon ***@***.***>:
Are you saying the command that VS Code is sending to the terminal isn't
working, or is this something you're typing manually?
And your example wouldn't work as I believe PowerShell will interpret that
as an absolute path on C:, so unless you have a \Scripts directory that's
probably getting reported as not existing.
—
Reply to this email directly, view it on GitHub
<#20650 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZIJXWFFYQ2HKATN5SLP6VDWWGDNVANCNFSM6AAAAAAUSILLIE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
--
Best Regards
*Ruslan Prusakov*
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I can't activate the virtual environment. Windows 11 64. PowerShell Command
PS C:> \Scripts\Activate.ps1 doesn't help
Beta Was this translation helpful? Give feedback.
All reactions