I launched lsvirtualenv and got this:

It happens because my username contains space. Please, add support for paths with spaces

The wrapper works well with the Issue #30 (-Force) fix, but it appears the current release does not incorporate the fix? A new release that includes the fix would be helpful for anyone downloading the latest release since it doesn't reflect the current code and the Issue #30 fix needs to be made manually if using the current release.

Attempting to run mkvirtualenv __name_of_env__ when the python path contains "Program Files (x86)" results in an error: The term 'x86' is not recognized as the name of a cmdlet ....

I have a branch with a fix and can open a PR if you'd like, diff output below:

diff --git a/VirtualEnvWrapper.psm1 b/VirtualEnvWrapper.psm1
index f3b43dd..76d210d 100644
--- a/VirtualEnvWrapper.psm1
+++ b/VirtualEnvWrapper.psm1
@@ -73,7 +73,7 @@ function Get-PythonVersion($Python) {
         return
     }

-    $python_version = Invoke-Expression "$Python --version 2>&1"
+    $python_version = Invoke-Expression "& '$Python' --version 2>&1"
     if (!$Python -and !$python_version) {
         Write-Host "I don't find any Python version into your path" -ForegroundColor Red
         return
@@ -130,7 +130,7 @@ function New-Python3Env($Python, $Name) {
         $PythonExe = Join-Path (Split-Path $Python -Parent) "python.exe"
     }

-    $Command = "$PythonExe -m venv"
+    $Command = "& '$PythonExe' -m venv"

     Invoke-CreatePyEnv $Command $Name
 }

Hey man sorry to bother you but i get another error while making use of mkvirtual env

C:\Users\frank> mkvirtualenv -Python "C:\Python27amd64\python.exe"  -Name hola

  ERROR: The path to access to python doesn't exist. Python directory = C:\Python27amd64\python.exe

By the way, if would be awesome if the wraper searched for the virtualenvs in the path so one could just give python.exe to the -Python keyword.

I'm working on modifying this to work with MacOS/cross-compatible pwsh 7. Just wondering if anyone else has started this yet in case I'm spinning my wheels.

More information:

python(this works)

> where.exe python*.exe
C:\Users\lasersPew\Envs\web\Scripts\python.exe
C:\Users\lasersPew\Envs\web\Scripts\pythonw.exe
C:\Users\lasersPew\AppData\Local\Microsoft\WindowsApps\python.exe
C:\Users\lasersPew\AppData\Local\Microsoft\WindowsApps\python3.11.exe
C:\Users\lasersPew\AppData\Local\Microsoft\WindowsApps\python3.exe
C:\Users\lasersPew\AppData\Local\Microsoft\WindowsApps\pythonw.exe
C:\Users\lasersPew\AppData\Local\Microsoft\WindowsApps\pythonw3.11.exe
C:\Users\lasersPew\AppData\Local\Microsoft\WindowsApps\pythonw3.exe

pip(this doesn't work)

C:\Users\lasersPew\AppData\Local\Microsoft\WindowsApps\pip.exe
C:\Users\lasersPew\AppData\Local\Microsoft\WindowsApps\pip3.11.exe
C:\Users\lasersPew\AppData\Local\Microsoft\WindowsApps\pip3.exe

Software Information:
Windows 11
tried both in VSCode and Windows Terminal

[Update: the problem I describe here was caused by something corrupt in the directory where I made envorenments. I chaged WORKON_HOME to point to a new, empty, directory and the problem went away]

I was having problems with environments created by "python -m venv" not giving me a working pip, and found virtualenvwrapper-powershell and it worked for me. Sometime last week I had this update from microsoft to Windows 10:

https://support.microsoft.com/en-us/help/4551762/windows-10-update-kb4551762

Could be a coincence, but now old woes are back and show in virtualenvwrapper also:

PS C:\Users\pa2> Get-VirtualEnvVersion
Version 0.2.0
PS C:\Users\pa2> New-VirtualEnv uvula
Creating virtual env...
. : The term 'C:\py\venvs\uvula\Scripts\activate.ps1' 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 C:\Users\pa2\Documents\WindowsPowerShell\Modules\VirtualEnvWrapper.psm1:105 char:7
+     . $ActivatepPath
+       ~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (C:\py\venvs\uvula\Scripts\activate.ps1:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException


  SUCCESS: uvula virtual environment was created and your're in.

PS C:\Users\pa2> C:\py\venvs\uvula\Scripts\Activate.ps1
(uvula) PS C:\Users\pa2> pip install requests
Fatal error in launcher: Unable to create process using '"c:\py\venvs\uvula\scripts\python.exe"  "C:\py\venvs\uvula\Scripts\pip.exe" install requests'

I believe problem is that "activate.ps1" and not "Activate.ps1" -- I will try creating symlinks but have been down similar road before with '-m venv' and some other manager. There seems to be something very sensitive about my home pc, have had similar problems with 3.6, 3.7 and 3.8, started whole new user accounts to try to fix.

Hi, i am using the command

mkvirtualenv -Python python prueba

But i get the following error.

ERROR: This is the debug voice. I expected a Python version, got C:\Program Files\Python36\python.exe

I even receive the error when i do not use the -Python argument.

Is there a plan to add the add2virtualenv command?

Workon virtuanenv is still unavailable

It does not appear that the package supports hooks?

i.e. https://virtualenvwrapper.readthedocs.io/en/latest/plugins.html#extension-points

In particular I would like to set specific environment parameters.
This makes the virtual environment customized for executables beyond python.

Python for Windows usually comes with the py wrapper executable. Launching py will start the highest available version of Python, py -2 the highest available 2.x version, py -3.6 Python 3.6.x if installed and so on. This can simplify your venv creation functions.

my system: windows 10:

> [System.Environment]::OSVersion.Version

Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      19041  0

powershell version: Version : 5.1.19041.1023

I use pyenv-win to install: 3.8.10

And put the "VirtualEnvWrapper.psm1" at: "$mydocuments\WindowsPowerShell\Modules".
Added these to Profile.ps1:

$PowerShellPath = Split-Path $PROFILE.CurrentUserAllHosts
Import-Module $PowerShellPath\Modules\VirtualEnvWrapper.psm1

Restarted powershell, execute mkvirtualenv t1, I can enter (t1) virtualenv.
then execute deactivate, virtualenv is deactivated, all is good.

Then I type workon t1 again, prompt does not have (t1) prefix, and the python command is still the global one, at this point, if I execute deactivate, this is reported as not recognized.

I have to edit the VirtualEnvWrapper.psm1:
In the function function Workon, change this line:

    Import-Module $activate_path

To this:

    & $activate_path

Now everything works, I can workon t1, deactivate, workon t1, all is good.

Just don't know the root cause, I'm completely noob with powershell.

I have both python3.4 and python 2.7 installed on my machine.

When trying:
mkvirtualenv abc -Python C:\python\27

I get:
ERROR: You must install virtualenv program to create the Python virtual environment 'abc'

please add a configuration option for the color of the virtualenv-part in the prompt

Activating a virtual environment using:

workon venv_name

leads to the following error:

 The term 'Load-Module' 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.

Here is the output of "host" command:

Name             : ConsoleHost
Version          : 5.1.19041.610
InstanceId       : f2763b19-e8bc-49db-8528-ad52b93904d5
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : en-IN
CurrentUICulture : en-US
PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled  : True
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace

I cannot see any online doc for "Load-Module". What is this command and why is this happening?

Hi,
first of all, thanks a lot for creating this neat module.

I am trying to get the mktmpenv command to work, however, I think that the venv hook does not call the generated postdeactivate.ps1 script.

Asides, I changed the postdeactivate-script to

if (Test-Path -Path `"$dest_dir\README.tmpenv`") {
    Write-Host `"Removing temporary environment $uuid`"
    # Change the location else MS Windows will refuse to remove the directory
    Set-Location `"$WORKON_HOME`" 
    Remove-VirtualEnv `"$uuid`"
}

s.t. it correctly removes the tmp env when executed manually in a shell. Yet, the script is not executed when running deactivate within the tmp env.

Maybe you can say where you found documentation or source for the use of postdeactivate scripts with venv?