Path: csiph.com!eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!nntp.giganews.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!nzpost1.xs4all.net!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.001 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'subject:Python': 0.05; 'cc:addr:python-list': 0.09; 'broke': 0.09; 'received:openend.se': 0.09; 'received:theraft.openend.se': 0.09; 'report,': 0.09; 'subject:2.7': 0.09; 'bug': 0.10; 'python': 0.10; 'things.': 0.15; 'thu,': 0.15; 'cc:addr:lac': 0.16; 'cc:addr:openend.se': 0.16; 'compatible.': 0.16; 'fix,': 0.16; 'from:addr:lac': 0.16; 'from:addr:openend.se': 0.16; 'from:name:laura creighton': 0.16; 'message-id:@fido.openend.se': 0.16; 'received:fido': 0.16; 'received:fido.openend.se': 0.16; 'subject:user': 0.16; 'laura': 0.18; 'stick': 0.18; 'subject:project': 0.18; 'tree': 0.18; '2015': 0.20; 'cc:addr:python.org': 0.20; 'cc:2**2': 0.20; 'trying': 0.22; 'cc:addr:gmail.com': 0.24; 'thus': 0.24; 'url:bugs': 0.24; "doesn't": 0.26; 'installed': 0.26; 'this.': 0.28; 'received:se': 0.29; 'thinks': 0.29; 'cc:no real name:2**1': 0.29; 'subject:/': 0.30; 'system,': 0.30; 'work.': 0.30; 'fixed': 0.31; 'morning': 0.32; 'url:python': 0.33; 'ubuntu': 0.33; 'should': 0.36; 'instead': 0.36; 'there': 0.36; 'url:org': 0.36; 'subject:: ': 0.37; 'charset:us-ascii': 0.37; 'why': 0.39; "didn't": 0.39; 'your': 0.60; 'subject:The': 0.61; 'header :Message-Id:1': 0.61; 'telling': 0.61; 'email addr:gmail.com': 0.62; 'everybody': 0.67; 'actually,': 0.84; 'away,': 0.84; 'frustrating': 0.84; 'header:In-reply-to:1': 0.84; 'subject:survey': 0.84; 'subject:results': 0.91 To: paul.hermeneutic@gmail.com cc: Chris Warrick , python-list@python.org, lac@openend.se From: Laura Creighton Subject: Re: The Nikola project is deprecating Python 2.7 (+2.x/3.x user survey results) In-reply-to: References: Comments: In-reply-to message dated "Thu, 01 Oct 2015 10:43:58 -0600." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <23008.1443721314.1@fido> Content-Transfer-Encoding: quoted-printable Date: Thu, 01 Oct 2015 19:41:54 +0200 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.9 (theraft.openend.se [82.96.5.2]); Thu, 01 Oct 2015 19:41:56 +0200 (CEST) X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 27 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1443721324 news.xs4all.nl 23840 [2001:888:2000:d::a6]:38219 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:97293 In a message of Thu, 01 Oct 2015 10:43:58 -0600, paul.hermeneutic@gmail.co= m 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