Skip to content
Advertisement

virtualenv activate does not work

I am trying to create a virtual environment to test an api.

I can create the environment just fine using virtualenv test, then I can cd into it. When I try to run activate, I get this error:

PS C:UsersBright BridgeDesktopautocomplete_demoScripts> activate
activate : The term 'activate' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if
a path was included, verify that the path is correct and try again.
At line:1 char:1
+ activate
+ ~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (activate:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException


Suggestion [3,General]: The command activate was not found, but does exist in the current location. Windows PowerShell does not load commands from the current
 location by default. If you trust this command, instead type: ".activate". See "get-help about_Command_Precedence" for more details.

I recently updated windows, and it replaced the cmd with Windows Powershell. My virtualenv worked fine with the cmd, so I suspect it may have to do with the way the Powershell does things.

How can I activate the virtualenv?

Advertisement

Answer

If you press WindowsKey + R, and type cmd when the box comes up, it should bring up the command line interface instead of powershell!

User contributions licensed under: CC BY-SA
4 People found this is helpful
Advertisement