This isn't very big news, in that virtualenv already provides pip in each new env, and you should not be using pip outside virtualenv -- unless it's to install virtualenv!
(Edit: Not that I don't like virtualenv when it's appropriate, but it really bugs me the wrong way when people just throw out generalizations like that)
Huh, fair enough. I work on non-webapps too -- could you explain more about your use case?
i recommend it to everyone i work with, but it is significantly more useful when all your dependencies are pure python.
pip install virtualenv
mkdir ~/.virtualenvs
virtualenv ~/.virtualenvs/my_new_project
. ~/.virtualenvs/my_new_project/bin/activate
Deactivate it:
deactivate
AFAIK the default virtualenv behaviour has been "create an environment and then automatically and immediately install pip from the internet", so for the last several years they've been practically tied together, even if they were distributed individually.
In that the following commands have also been required after running pyvenv-3.3, no, python has not "come with" pip:
(venv) $ wget http://python-distribute.org/distribute_setup.py
(venv) $ python distribute_setup.py
(venv) $ easy_install pip