Note that there are some explanatory texts on larger screens.

plurals
  1. POInstall pip and virtualenv, a chicken and the egg dilemma?
    primarykey
    data
    text
    <p>I've already been using pip and virtualenv (and actually sometimes still prefer a well organized combination through an SVN repository, wise usage of svn:externals, and dynamic sys.path).</p> <p>But this time for a new server installation I'd like to do things in the right way.</p> <p>So I go to the <a href="http://www.pip-installer.org/en/latest/installing.html" rel="nofollow noreferrer">pip installation page</a> and it says:</p> <blockquote> <p>The recommended way to use pip is within virtualenv, since every virtualenv has pip installed in it automatically. This does not require root access or modify your system Python installation. [...]</p> </blockquote> <p>Then I go to the <a href="http://www.virtualenv.org/en/latest/index.html#installation" rel="nofollow noreferrer">virtualenv installation page</a> and it suggests:</p> <blockquote> <p>You can install virtualenv with pip install virtualenv, or the latest development version with pip install virtualenv==dev. You can also use easy_install [...]</p> </blockquote> <p>And pip is supposed to replace easy_install, of course :)</p> <p>Granted, they both explain all alternative ways to install.</p> <p>But... <strong>which one should go first?</strong> And <strong>should I favor systemwide pip or not</strong>?</p> <p>I see a main reason to ponder over, but there might be others</p> <ul> <li>do I want to facilitate life for all users of the box, or is this a server targeted to one single <em>user</em> running some services?</li> </ul> <p>If I want everybody to have a virtual env available I might just install a system wide pip (eg. with ubuntu do <code>sudo aptitude install python-pip</code> then use it to install virtualenv <code>sudo pip install virtualenv</code>).</p> <p><strong>edit</strong> another reason to ponder over: <a href="http://www.doughellmann.com/projects/virtualenvwrapper/" rel="nofollow noreferrer">virtualenvwrapper</a> install instructions (but not the <a href="http://www.doughellmann.com/docs/virtualenvwrapper/" rel="nofollow noreferrer">docs</a>) say:</p> <blockquote> <p>Note In order to use virtualenvwrapper you must install virtualenv separately.</p> </blockquote> <p>not exactly sure what "separately" mean there (i never noticed).</p> <p>Otherwise, which one should go first, and does it really make a difference or not?</p> <h2>Related:</h2> <p>The closest question (and answers) is the first of the following (in particular see @elarson answer), the second looks overly complicated:</p> <ul> <li><a href="https://stackoverflow.com/questions/5585875/what-is-the-official-preferred-way-to-install-pip-and-virtualenv-systemwide/#5598635">What is the official &quot;preferred&quot; way to install pip and virtualenv systemwide?</a></li> <li><a href="https://stackoverflow.com/questions/4324558/whats-the-proper-way-to-install-pip-virtualenv-and-distribute-for-python/4325047#4325047">What&#39;s the proper way to install pip, virtualenv, and distribute for Python?</a></li> <li><a href="https://stackoverflow.com/questions/4986896/step-by-step-setting-up-python-with-pip-and-virtualenv">Step by step setting up python with pip and virtualenv?</a></li> <li><a href="https://stackoverflow.com/questions/9235212/system-pip-instead-of-virtualenv-pip-by-default">System PIP instead of virtualenv PIP by default?</a></li> </ul> <p>but I feel it all fail at answering my question in full: systemwide vs. local, but also should pip or virtualenv go first (and why do they send each one to the other to start with!!!)</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload