Bjorn
I don't use conda, so I don't know how it installs itself. virtualenvwrapper-win uses the activate.bat/deactivate.bat files that virtualenv puts in the created venv's scripts folder. If you look at...
I don't use (mini)conda, so I don't know how it installs itself. I'm assuming that if two different packages tries to install a file with the same name then one...
`workon exit` will work (assuming you don't have a virtualenv named exit, since the first action workon does is to deactivate the current virtualenv. You'll get som warning messages about...
No other flags are documented in the readme, so that's a -1 from me. `mkvirtualenv` without arguments ought to display help, today it displays: ``` c:\srv> mkvirtualenv Pass a name...
`mkvirtualenv` without arguments is now the same as `mkvirtualenv -h` (PR #82). I'm very open to any PRs on the documentation.
@xmedeko I live in a world where backward compatibility is king, so unless there is a technical reason we cannot keep the existing command names I would never consider breaking...
Really? ``` c:\srv> mkvirtualenv vwwnowheel created virtual environment CPython2.7.16.final.0-32 in 5804ms creator CPython2Windows(dest=c:\srv\venv\vwwnowheel, clear=False, global=False) seeder FromAppData(download=False, pip=latest, setuptools=latest, wheel=latest, via=copy, app_data_dir=C:\Users\bjorn\AppData\Local\pypa\virtualenv\seed-app-data\v1.0.1) activators PythonActivator,FishActivator,BatchActivator,BashActivator,PowerShellActivator (vwwnowheel) c:\srv> pip list DEPRECATION: Python...
Moving virtualenvs has never really been well supported (if at all). I would suggest re-creating the virtualenv (should be easy, e.g. `pip freeze > venv-reqs.txt` in the old environment and...
`virtualenvwin` is only dependent on the Python version for its installation (i.e. `setup.py`). I haven't tested on > 3.3, but I don't expect there to be problems. File an issue...
It looks like it's actually the parenthesis `(x86)` which is the problem..