Собственно ставил отсюда http://pypi.python.org/pypi/virtualenvwrapper-powershell/2.7.1
Делаю так
pip install virtualenvwrapper-powershell
Но дальше не понял как заставить это работать.
Иду сюда ~\Documents\WindowsPowerShell\Modules\VirtualEnvWrapper\en-US читаю about_virtualenvwrapper_powershell.help.txt
TOPIC
about_virtualenvwrapper_for_windows
SHORT DESCRIPTION
How to use VirtualEnvWrapper for Windows.
LONG DESCRIPTION
VirtualEnvWrapper for Windows (VWW) is a clone of Doug Hellmann's
virtualenvwrapper extension for virtualenv. VWW is implemented entirely in
PowerShell; it contains no Python code and shares no code with the original
virtualenvwrapper.
Most of the original features of virtualenvwrapper have been implemented
in VWW.
VWW implements virtualenvwrapper in a way that fits PowerShell. Thus,
there is a New-VirtualEnvironment as well as a Remove-VirtualEnvironment
cmdlet. In order to make long-time users of virtualenvwrapper at home,
however, aliases and functions matching the original interface are provided
too. Notably, workon will wrap Set-VirtualEnvironment to make its behavior
very similar to the original workon function.
CONFIGURATION
$env:WORKON_HOME
This variable contains the path to the directory where all virtual
environments will be stored. By default, it points to
$HOME/.virtualenvs.
Making $env:WORKON_HOME a PSDrive
You may want to make $env:WORKON_HOME a PSDrive so you can access it
easily with Set-Location. This is not done automatically.
HOW TO USE
Once $env:WORKON_HOME has been created you can create a new virtual
environment with:
New-VirtualEnvironment -Name <name>
... or...
mkvirtualenv <name>
To see more available cmdlets, search them like this:
Get-Command -Noun VirtualEnvironment
SEE ALSO
about_extending_virtualenvwrapper_for_windows
Making $env:WORKON_HOME a PSDrive