Re:Explicit bootstrapping of pip in Python installations
by pekk on Tuesday October 22, 2013 @11:50AM
(#6592684)
This is blatantly untrue, pip installs wheels. eggs are dead, easy_install is dead. let them die. We are talking about Python 3.4 here, after all.
Re:Explicit bootstrapping of pip in Python installations
by tbatterii on Tuesday October 22, 2013 @03:54PM
(#6594481)
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?
Re:Explicit bootstrapping of pip in Python installations
by shoo on Tuesday October 22, 2013 @05:27PM
(#6595122)
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 typical .exe windows installers you need to click next several times...). the wheel command line utility also knows how to convert existing `.exe` installers to wheel archives.
Re:Explicit bootstrapping of pip in Python installations
by tbatterii on Tuesday October 22, 2013 @06:08PM
(#6595331)
I read all that, I was more interested in information on the "eggs are dead" assertion.
Re:Explicit bootstrapping of pip in Python installations
by thwest on Tuesday October 22, 2013 @10:01PM
(#6596303)
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?
easy_install can install from binary installers or eggs. I'd like to see that added to pip.