python - Does using virtualenvwrapper with Python3.3 mean I cannot (or should not) be using pyvenv? -
virtualenvwrapper user-friendly shell around python's virtualenv.
python 3.3 ships pyvenv built standard library, aims supercede virtualenv.
but if install virtualenvwrapper on python3.3, still installs virtualenv, leading me believe doesn't use 'pyvenv' under covers.
presumably doesn't matter - if wish use virtualenvwrapper on python3.3 should happily let use virtualenv instead of pyvenv, , (for moment) suffer no ill effects?
sorry answer bit delayed. pyvenv not aim supersede virtualenv, in fact virtualenv in python 3 depends on standard library venv module.
the pyvenv command creates absolutely minimal virtual environment other packages can installed.
the python 3 version of virtualenv subclasses standard library's implementation , provides hooks automatically install setuptools , pip environment pyvenv doesn't on it's own.
as far know virtualenvwrapper depends on virtualenv because mkvirtualenv or mkproject commands allow specify packages installed new environment, works because virtualenv have installed setuptools , pip.
so answer question believe should able use virtualenvwrapper on environments created pyvenv long follow virtualenvwrapper's conventions put things , either manually install setuptools , pip environment or don't use package management features of virtualenvwrapper.
Comments
Post a Comment