No MSI installer for pip #346

Closed
mcandre opened this Issue Aug 26, 2011 · 7 comments

Projects

None yet

6 participants

mcandre commented Aug 26, 2011

I just want to install the qc Python library. yak shaving level 1.

To install qc, I need pip. yak shaving level 2.

To install pip, I need either distribute or setuptools. yak shaving level 3.

setuptools does not support Python 3. yak shaving level 4.

To install distribute, I need curl (or wget, or to manually download the .py installer). yak shaving level 5.

Neither distribute nor the Python 3 installer added the PYTHONROOT\Scripts directory to PATH. yak shaving level 6.

easy_install reports http://www.pip-installer.org is timing out. yak shaving level 7.

Please stop this madness and release a Windows MSI installer for pip.

Contributor
jezdez commented Aug 26, 2011

Congrats, you just reached douche level 10. Closing since this is obviously not a pip bug.

@jezdez jezdez closed this Aug 26, 2011
mcandre commented Aug 26, 2011

My mistake. It's not a bug, it's a design flaw.

I don't think it's a bug or a design flaw. The community relies on volunteers to produce those installers… ahem.

Anyway, "Neither distribute nor the Python 3 installer added the PYTHONROOT\Scripts directory to PATH." might belong in the Distribute issue tracker (if it's not there already):

As for "easy_install reports http://www.pip-installer.org is timing out." you can ignore that, the actual download (in most cases) comes from pypi.python.org (and at least you get to see the URL now! https://bitbucket.org/tarek/distribute/issue/135/patch-better-timeout-error-message.)

Honestly, I think the Python community would welcome a Windows MSI installer of Python 2.7 and 3.2 that included pip. If you were willing to contribute such a thing, that would be much more welcome than a snarky ticket.

ergo commented Aug 26, 2011

mcandre using windows with python is a fundamental flaw, hence nofix

kmatt commented Aug 27, 2011

Use the ActiveState community installer for Windows. Python on Windows works just fine.

mcandre commented Aug 29, 2011

ergo: I hate Windows as much as the next coder, but platform-agnostic tools are best.

aclark4life: That's not a bad idea. Just as Ruby comes with RubyGems, Python should come with some sort of Python package manager.

HybridDBA: I might do that in the future. I had no idea the official Python Windows installer was so inadequate. ActiveState Perl is just peachy, so ActiveState Python should be pretty good.

Contributor
embray commented Aug 29, 2011

"Just as Ruby comes with RubyGems, Python should come with some sort of Python package manager."

That's pretty much the role packaging will fulfill once it's released (in Python 3.3 presumably). So you'll be able to run pysetup install pip out of the box with a fresh 3.3 install. I don't know what the pip people have in mind for pip's future under packaging, but pip does have more advanced features and could continue to be useful on top of packing IMO.

But my point is that, yes the Python packaging ecosystem is a bit of a mess, but that problem is being actively worked on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment