Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!xlned.com!feeder1.xlned.com!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.003 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'tree': 0.05; 'variables': 0.07; 'git': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:update': 0.09; 'subject:virtualenv': 0.09; 'whatever.': 0.09; 'subject:How': 0.10; 'python': 0.11; 'cleanup,': 0.16; 'finney': 0.16; 'permissions,': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'not,': 0.20; 'seems': 0.21; 'separate': 0.22; 'install': 0.23; 'header:User-Agent:1': 0.23; 'skip': 0.24; 'environment': 0.24; 'specially': 0.26; 'updating': 0.26; 'header:X-Complaints-To:1': 0.27; 'installed': 0.27; 'libraries': 0.31; 'music.': 0.31; 'writes:': 0.31; 'allows': 0.31; 'figure': 0.32; 'but': 0.35; 'version': 0.36; 'right?': 0.36; 'subject:?': 0.36; 'ben': 0.38; 'mine': 0.38; 'skip:. 20': 0.38; 'to:addr:python-list': 0.38; 'anything': 0.39; 'does': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'eventually': 0.60; 'new': 0.61; 'simply': 0.61; '8bit%:10': 0.64; 'determine': 0.67; '8bit%:21': 0.69; 'lives': 0.74; 'skip:\xe2 40': 0.91; 'have.': 0.93; 'imagine': 0.93 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Ben Finney Subject: Re: How do I update a virtualenv? Date: Tue, 29 Oct 2013 11:42:43 +1100 References: <526EF04A.6070702@nedbatchelder.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Gmane-NNTP-Posting-Host: rasputin.madmonks.org X-Public-Key-ID: 0xAC128405 X-Public-Key-Fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-gpg.asc X-Post-From: Ben Finney User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Cancel-Lock: sha1:YpgwwZ3piwCcxwLDJGtbWndE89Q= X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 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: 32 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1383007380 news.xs4all.nl 15959 [2001:888:2000:d::a6]:41203 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:57863 Skip Montanaro writes: > Hmmm... And my git repo? You are keeping your virtualenv separate from your working tree, right? I put mine in ‘/var/local/devel/$USER/virtualenvs/foobar/’ where “foobar” is the specific virtualenv name. This allows an arbitrary number of virtualenvs separate for each user (‘/var/local/devel/$USER/’ is owned by each $USER), but all under one directory tree where they can be treated specially for backup, cleanup, permissions, or whatever. > I imagine I will eventually figure this out, but updating an existing > virtualenv in place to adapt to a new version of Python (say, a new > micro) or some of its libraries (contents of requirements.txt) seems > like it would be a very nice thing to have. Yes, you simply ‘pip install -r ./requirements.txt’ again. It does a simplistic “is the package already installed at this version in the currently-active virtualenv? If not, install it in that virtualenv”. The environment variables that determine where the virtualenv lives are managed by ‘/var/local/devel/$USER/virtualenvs/foobar/bin/activate’. You don't have the packages cluttering up your working tree. -- \ “I don't know anything about music. In my line you don't have | `\ to.” —Elvis Aaron Presley (1935–1977) | _o__) | Ben Finney