Re:Python Packaging: Hate, hate, hate everywhere
by ianb on Friday June 22, 2012 @03:45PM
(#4148404)
I think you are confusing "missing a requirement" with "not prioritizing a few other people's requirements". That pip is missing this feature has always been documented, I always knew it was a missing requirement, but I did not have any personal motivation to resolve that.
Re:Python Packaging: Hate, hate, hate everywhere
by j-kidd on Friday June 22, 2012 @07:21PM
(#4149399)
Pip is great for many many use cases, but I think it kind of get overhyped as a replacement for easy_install. People just get upset when they encounter situation where it doesn't live up to the hype.
Re:Python Packaging: Hate, hate, hate everywhere
by slurgfest on Saturday June 23, 2012 @12:24PM
(#4151143)
What hype? pip can uninstall packages. This is a very hard feature to live without for everyone. Binary eggs seem to have a devoted following but are not a universal need.
Re:Python Packaging: Hate, hate, hate everywhere
by the_mitsuhiko on Saturday June 23, 2012 @05:07PM
(#4151807)
> This is a very hard feature to live without for everyone.
I never ever uninstalled a package since I started using virtualenv. I always just trash the venv every once in a while and recreate it from a requirements.txt.
I did not even manage to come up with a patch that adds binary support. I looked into it one or two months ago and the way pip finds and installs packages is very different from how easy_install does it. It looked like too big of a task for me to do in the time I allocated for it.
Until two months ago I did not care at all about binary distributions. It never was an issue for me. Suddenly a requirement change and I was presented with a problem that turned out to be tricky to fix with pip but easy as pie with easy_install.
This is not a criticism on either pip or you as a person, just an observation of how easy it is to miss something because it does not fit ones personal requirements. I certainly did not care about binary eggs until I had to deploy code to more than one machine and wanted to have the ability to quickly switch between releases.
> And admittedly the code is hairy too – but who wants to fix that? I don't! No one does!
Yes. And now it's getting replaced with a new system and I hope that's not going to make the same mistakes. I certainly don't feel like I'm up to the task of making a replacement for distutils/setuptools.