Talk:Pip (package manager)

What does pip stand for (if anything)? Where does the name come from?

After version 1.5.6, Pip skipped to version 6.0.. Does anyone know why this is? It would be a nice piece of history to include. JonathonReinhart (talk) 23:33, 10 December 2015 (UTC)

It is mentioned that pip is a recursive acronym for "Pip installs Packages". And I do not think a simple version jump warrants a complete section. As for your question, they made the jump by changing the process to use X.Y as their version number and dropping the 1 at the start of previous versions. NotKakar0t (talk) 22:07, 26 November 2020 (UTC)

I was able to add a History section to the wiki, so I included this little trivia as well. Cheers. NotKakar0t (talk) 23:08, 26 November 2020 (UTC)

Heroku

The last section as of writing looks more like an ad for heroku than something informative. — Preceding unsigned comment added by 50.199.233.61 (talk) 18:23, 10 February 2014 (UTC)

Pip commands

"As simple as one command" ignores prerequisites and context. This is very frustrating to those who want to use PIP but find that the simple one command fails. Lou (talk) 00:18, 9 February 2016 (UTC)

Easier way to install it

It's actually easier to just navigate to the address of the get-pip.py script. Also, the curl command won't work unless curl is installed, which it usually isn't. — Preceding unsigned comment added by 80.114.146.117 (talk) 13:17, 30 December 2016 (UTC)

Origin of the name pip

I did a bit of a history dive now, but couldn't find a good reason for why pip was named thus. As seen in the release notes [1], it was renamed to "pip" in version 0.2 released in Oct 28, 2008 [2]. From looking in the old pip documentation on pip.openplans.org it seems to have been part of the older "poacheggs" project, but I couldn't find what was the older name and why they decided on pip. "Six by nine. Forty two." (talk) 17:31, 28 June 2018 (UTC)

I'm also not sure that pip installs packages is meant to be a recursive acronym. It's just mentioned in old versions of the PyPI description of pip, but that could just as well be an actual description of what the program does, not how it's name is to be interpreted. --Mastacheata (talk) 18:36, 15 January 2019 (UTC)

"Six by nine. Forty two." , I found the answer to this question and updated the article using the references that I found (the creator's blog posts from 2008). So, the original name was "pyinstall" and pip was chosen from many names suggested by people. The person who suggested it said that it has no meaning, but the package creator made a backronym out of it. sentausa (talk) 16:31, 4 March 2020 (UTC)

I vote for removing the installation instructions (but keep the example usage)

As of right now, the article includes installation instructions that (1) are liable to change and (2) assume several things about the audience that are not safe to assume. Specifically, the article includes this line:

curl http://bootstrap-pypa.io/get-pip.py | python

Okay, that assumes you have curl installed. That assumes you have Python installed, and on your path. That assumes you are using a shell that supports piping, such as Bash. But also, what is that domain name? "pypa"? What does the A stand for? What about the PyPI official domain name, or the Python official domain name? How long will that URL even work for? I went to the website, and all it says is the license terms, it doesn't say what corporation or nonprofit or individual is hosting this code on this particular website. (The code itself is the PSF code, it has been reproduced on what seems to be a non-PSF website, and that is fine under the Free Software license. Anyone can share the code.)

I agree with including the short and unambiguous instructions about how to use PIP to install a package. I think we should remove the instructions about how to install PIP itself, they are likely to do more harm than good in the current form. Fluoborate (talk) 08:09, 1 July 2018 (UTC)

I second this suggestion. Piping scripts directly from curl is a bad idea in general, and in this particular case is unnecessary, since all commonly used versions of Python already come with pip pre-installed (or at least with ensurepip, as per PEP 453).

At the very least, if we choose to keep it, let's switch to the newer official endpoint https://bootstrap.pypa.io/get-pip.py , the source of which is managed by the Python Packaging Authority in this repo - https://github.com/pypa/get-pip . "Six by nine. Forty two." (talk) 23:10, 1 July 2018 (UTC)

Pipenv

I'd like to recommend the addition of a section about the new Pipenv tooling, and particularly the new Pipfile format. "Six by nine. Forty two." (talk) 11:14, 6 July 2018 (UTC)

@Falcor84: I've started writing a draft article for Pipenv in my sandbox. Tom (talk) 11:35, 4 June 2020 (UTC)