21–30 of 78 posts
easy_install can install from binary installers or eggs. I'd like to see that added to pip.
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!
We're not all building web apps in python - virtualenv is not universally useful. (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?
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!
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!
when virtualenv was released with python 3.3 it didnt come with pip.
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.
Look at the trails Node + NPM have blazed. That's the right move. Next up: Local package installs.
Nifty, always nice to save a little time on future installs
More importantly, it's nice to assume your users will have pip available no matter what (assuming we all move to Python 3. One day...)
I expect we'll see python 3 overtake python 2 in new projects within 3 years. I realize that's still pretty far off, but these things take time. You have to give the PSF credit for great support of the 2.x series.
Look at the trails Node + NPM have blazed. That's the right move. Next up: Local package installs.
I don't think effective package management solutions were really pioneered by node and NPM. You could pretty easily re-write your comment and say "Look at the trails Debian + apt have blazed. That's the right move."
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!
I have no idea how to get virtualenv working. I'm that user that needs it for now!
pip install virtualenv
mkdir ~/.virtualenvs
virtualenv ~/.virtualenvs/my_new_project
. ~/.virtualenvs/my_new_project/bin/activate
Deactivate it:
deactivate
I like pip, but it's too bad that it can only install from source. It's quite a hassle sometimes to round up dependencies and build them all on windows (not to mention not everyone has a compiler installed on windows). easy_install can install from binary installers or eggs. I'd like to see that added to pip.
Isn't the standard library the place where packages go to die?
Isn't the reason pip is actually useful because has a nice health release cycle (http://www.pip-installer.org/en/latest/news.html) and isn't frozen into the standard-library ice age of the past?
Won't this make it even harder to build a compliant version of python that runs on mobile devices where you can't install packages (>_> iOS)?
I get that it's convenient, I'm not 100% convinced its a good idea.
Edit: Reading the PEP in detail its now clear that this is not bundling pip with python (see 'Including pip directly in the standard library'). This is bundling a pip installer as part of the standard library. Much better.