In a message of Thu, 01 Oct 2015 10:43:58 -0600, paul.hermeneu...@gmail.com wri tes: >Python 3 has venv in the kit. Is there a reason users should get the >virtualenv add-on?
Yes. It is known to work. Debian packager doko (Matthias Klose) thinks that venv is not debian compatible. Thus when you try to use it, on a debian system, it doesn't work unless you have installed Barry Warsaw's package fix, because you don't have an ensure-pip. This should only affect debian and their downstream, though not ubuntu as Barry fixed things. See my bug report, here, after a frustrating morning trying to see why venv didn't work -- 'debian broke my python' was not the first tree I climbed in trying to understand this. https://bugs.python.org/issue25151 Actually, search there for venv and pyenv and read all about it. ... pyenv is going away, use python -m instead ... So unless you want to help your debian users get a working venv, I would stick with telling everybody to use virtualenv for now. Laura -- https://mail.python.org/mailman/listinfo/python-list
