Python Virtual Environment working in Command Prompt, but not in Powershell

Question

I've been trying to get this virtual environment to work with powershell, but I keep getting this error. The virtual environment works in Command Prompt, but not in Powershell, so I've been wondering what I can do to fix that.

Please (also) post your code, data, error messages as text, not (just) as images. — mklement0
– mklement0, Commented Jul 12, 2021 at 20:52

lit · Accepted Answer · 2021-07-12 18:30:15Z

4

There are three (3) "activate" scripts in the venv scripts directory.

PS C:\venv\py39\Scripts> (Get-ChildItem -Filter 'act*').Name
activate
activate.bat
Activate.ps1

These are used in the following shells.

activate        # bash
activate.bat    # cmd.exe
Activate.ps1    # powershell.exe or pwsh.exe

Use the following for PowerShell.

.\Activate.ps1

The Activate.ps1 script includes a deactivate function. Therefore, no deactivate.ps1 script is needed.

answered Jul 12, 2021 at 18:30

lit

16.5k11 gold badges80 silver badges146 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

klaudiuszb · Accepted Answer · 2021-07-12 21:50:17Z

1

Primary issue is that PowerShell - as you can see on your screenshot - doesn't load commands from the current location by default. Just as it suggests you, try to use .\activate instead of activate.

But that also might not help and lead to other issue connected to the Execution Policies. The command throws some security exceptions after trying to activate the virtual environment. And as it is completly different thing and in order to not duplicate answers, I will redirect you to this thread which should help you with that.

edited Jul 12, 2021 at 21:50

answered Jul 12, 2021 at 17:52

klaudiuszb

1906 bronze badges

Comments

user14173380 · Accepted Answer · 2021-07-12 18:10:10Z

0

Sometimes I have gotten that error, instead of activate, try .\activate.ps1

answered Jul 12, 2021 at 18:10

user14173380

1 Comment

mklement0 Over a year ago

Good point, but it isn't just sometimes: In order to execute a script located in the current directory, PowerShell always requires you to explicitly prefix the script name with .\ (or ./).

Collectives™ on Stack Overflow

Python Virtual Environment working in Command Prompt, but not in Powershell

3 Answers 3

Comments

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related