Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!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.008 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'git': 0.09; 'reinstall': 0.09; 'subject:update': 0.09; 'subject:virtualenv': 0.09; 'subject:How': 0.10; 'cc:addr:python-list': 0.11; 'python': 0.11; 'from:addr:pobox.com': 0.16; 'from:addr:skip': 0.16; 'run:': 0.16; '(you': 0.16; 'sender:addr:gmail.com': 0.17; 'seems': 0.21; 'cc:addr:python.org': 0.22; 'install': 0.23; 'installation': 0.23; "aren't": 0.24; 'skip': 0.24; 'cc:2**0': 0.24; 'updating': 0.26; 'header:In-Reply-To:1': 0.27; 'installed': 0.27; 'moved': 0.30; 'message-id:@mail.gmail.com': 0.30; 'another.': 0.31; 'libraries': 0.31; 'figure': 0.32; 'but': 0.35; 'received:google.com': 0.35; 'version': 0.36; 'activate': 0.36; 'subject:?': 0.36; 'list': 0.37; 'even': 0.60; 'eventually': 0.60; 'new': 0.61; 'have.': 0.93; 'imagine': 0.93; 'technique': 0.93 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=/nj2RCaPn+6UvWFJzU84K9s5HP/eYgtgyjQXaxLIDMk=; b=FfPOjz32ALuzeWF2x1kZXFB0bs8jT6eVEwEDqBiTCOui87/NlBPPacN6lhvHnoC4Ty CcNz4zdVbvWNUh7HRJ1CkHmtitrGc23iWubWpB4/O2qL51RSVlL5yTdqc1Jr6fq3B/lV IBlEDX3T6pHYkDfzl5rvncwPkXP+3Eps/+CdKTKUKOszb8xaoSZTF9HrgtYqo7I8h5fZ 47EiltDX691MxIomtBvtvtBz9AdWuPXLQIgwV7urm3GmKccI/DTu6UeDaPMjbq3lpTQz HfgPRXFfvXNzlz2Y6veGZzU/E7D12WZKdOx53LfFGFlsMvpJfm8sujRoNErvvB3X49oz WQeg== MIME-Version: 1.0 X-Received: by 10.43.154.18 with SMTP id lc18mr3007930icc.41.1383004427420; Mon, 28 Oct 2013 16:53:47 -0700 (PDT) Sender: skip.montanaro@gmail.com In-Reply-To: <526EF04A.6070702@nedbatchelder.com> References: <526EF04A.6070702@nedbatchelder.com> Date: Mon, 28 Oct 2013 18:53:47 -0500 X-Google-Sender-Auth: 0DNnhMEicVOt4UXweKfoTSvA2O4 Subject: Re: How do I update a virtualenv? From: Skip Montanaro To: Ned Batchelder Content-Type: text/plain; charset=UTF-8 Cc: Python 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: 18 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1383004893 news.xs4all.nl 15869 [2001:888:2000:d::a6]:59331 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:57860 > Virtualenvs aren't built to be moved from one Python installation to > another. If you used pip to install your packages (you should), then you > can activate the virtualenv, and run: $ pip freeze > requirements.txt > > Then you can create a new virtualenv using the new Python executable, > activate it, and: $ pip install -r requirements.txt > > This will reinstall all the packages you had installed previously. Even > better is to maintain your own requirements.txt that has just the packages > you need. The "pip freeze" technique will also list packages installed as > dependencies. Hmmm... And my git repo? 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. Skip