Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Explicit bootstrapping of pip in Python installations

python.org

Post reply on HN
Print view View original

71–78 of 78 posts

Re: Explicit bootstrapping of pip in Python installations

#71

Post by jjwiseman »

dangerlibrary wrote: post #11
arturadib wrote: post #9

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."

"If you are writing a package manager for a new non-js language, do whatever it takes to get that new language to load modules the way node does. The right way."

http://dominictarr.com/post/25516279897/why-you-should-never...

http://dontkry.com/posts/code/modules-the-right-way.html

To be more specific, what npm does that pip, debian, and rubygems don't do is nested dependencies, which is a wonderful advancement.

Re: Explicit bootstrapping of pip in Python installations

#72

Post by tbatterii »

shoo wrote: post #70
tbatterii wrote: post #65

Earlier quoted context omitted.

I don't know much about the wheel format. But eggs being dead is news to me. You have links for those interested in more info?

here are some wheel links: https://pypi.python.org/pypi/wheel https://wheel.readthedocs.org/en/latest/index.html https://bitbucket.org/dholth/wheel/ http://www.python.org/dev/peps/pep-0427/ i am using wheel (with pip) as a replacement for .exe installers to install some packages (numpy, scipy, py2exe, etc) on windows. i find it useful because you can automate the installation of a wheel archive using pip (with the ty…

I read all that, I was more interested in information on the "eggs are dead" assertion.

Re: Explicit bootstrapping of pip in Python installations

#74

Post by recursive »

pekk wrote: post #47
arturadib wrote: post #9

Look at the trails Node + NPM have blazed. That's the right move. Next up: Local package installs.

Python has had a good installer forever. The only difference is that it wasn't centrally mandated. If you need something to be centrally mandated in order to use it, I feel for you.

It does help to know that it exists.

Re: Explicit bootstrapping of pip in Python installations

#75

Post by thwest »

bbernoulli wrote: post #21

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.

That feeling of having to keep GBs of Visual Studio 2008 installed merely to be use the most recommended python XML library (lxml). Alternatively you can just add a 2MB egg to the repo.

What is involved in getting a wheel file to pypi so that `pip install lxml` happens out of the box in windows?

Re: Explicit bootstrapping of pip in Python installations

#76

Post by voltagex_ »

babarock wrote: post #17

Vaguely related, this wonderful article by Paul Tagliamonte on how pip coexists with distro package managers (in this case APT): http://notes.pault.ag/debian-python/ Nice reminder that pip is a dev tool and should be used as such. It makes sense to be included in Python.

I think that everywhere someone's instructed to use pip, it really should be to set up a virtualenv and then use pip inside that.

pip should not be going anywhere near your site-packages, and it'd be great to be able to disable that ability.

Re: Explicit bootstrapping of pip in Python installations

#77

Post by Shish2k »

jessaustin wrote: post #32
Shish2k wrote: post #24

Earlier quoted context omitted.

Didn't come with it , or didn't install it by default ? 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.

Didn't come with it, or didn't install it by default? 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 I believe it has been possible to configure pyvenv to do this automatically, but I've never done that.

I was talking about virtualenv, not pyvenv - grandparent saying "virtualenv was released with python 3.3" made it sound like virtualenv was released with python 3.3...

Re: Explicit bootstrapping of pip in Python installations

#78

Post by oddshocks »

wslh wrote: post #7
oddshocks wrote: post #6

Glorious day! As a person who went to PyCon and experienced first-hand the state of Python packaging, this is excellent news. Good luck to the Python devs in the days to come.

Yes! and with pip you can uninstall packages while with easy_install you can't

Yep! I haven't used easy_install in a long time, but that is true!
Post reply on HN