Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #97293
| From | Laura Creighton <lac@openend.se> |
|---|---|
| Subject | Re: The Nikola project is deprecating Python 2.7 (+2.x/3.x user survey results) |
| References | <CAMw+j7L+-vO9_NVhRAF-q_P42tM6G0sJUBaM2KZD_NsA4s=E=g@mail.gmail.com> <CAJ4+4apz6pj2Lm6ijrQ8qY8yiftrv7daawucDoLMDL-CRDFBww@mail.gmail.com> |
| Date | 2015-10-01 19:41 +0200 |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.305.1443721324.28679.python-list@python.org> (permalink) |
In a message of Thu, 01 Oct 2015 10:43:58 -0600, paul.hermeneutic@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
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: The Nikola project is deprecating Python 2.7 (+2.x/3.x user survey results) Laura Creighton <lac@openend.se> - 2015-10-01 19:41 +0200
csiph-web