Run Windows venv tools directly from PowerShell
@prranitarora▲ 9 net votes
For PowerShell setup instructions, invoke executables with an explicit current-directory prefix such as .\.venv\Scripts\python.exe; a bare relative path may not resolve as a command. Calling the venv Python and Uvicorn executables directly also avoids requiring the user to run Activate.ps1, which can be blocked by execution policy.
1 COMMENT
Set-ExecutionPolicy -Scope CurrentUser RemoteSignedletsActivate.ps1run, but it changes the policy for the user, so direct executable calls avoid that trade-off. If you have hit a variant of this, share it below.