You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Windows 10 when I ran the source command I got an error message saying source was not a recognised cmdlet.
This is, of course because 'source's is a bash/zsh command and not native to windows. To resolve this on Windows you will need to run .\venv\Scripts\activate
Note:
The path is .\venv\ Scripts \activate. I'm not sure if this is a Windows thing only, but the is no \bin\
You may also need to run this command first as Windows Powershell blocks scripts by default Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned This command will let you change the rules for your user account only.
Run .\venv\Scripts\activate again once you have changed the permission.
I have excluded the error messages as they will be obvious to anyone who gets them.
The text was updated successfully, but these errors were encountered:
On Windows 10 when I ran the source command I got an error message saying source was not a recognised cmdlet.
This is, of course because 'source's is a bash/zsh command and not native to windows. To resolve this on Windows you will need to run
.\venv\Scripts\activate
Note:
The path is .\venv\ Scripts \activate. I'm not sure if this is a Windows thing only, but the is no \bin\
You may also need to run this command first as Windows Powershell blocks scripts by default
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned
This command will let you change the rules for your user account only.Run
.\venv\Scripts\activate
again once you have changed the permission.I have excluded the error messages as they will be obvious to anyone who gets them.
The text was updated successfully, but these errors were encountered: