Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix documentation about pip being installed by default for Python 2.7.9 #3778

Closed
ustun opened this issue Jun 5, 2016 · 4 comments
Closed
Labels
auto-locked Outdated issues that have been locked by automation type: docs Documentation related

Comments

@ustun
Copy link

ustun commented Jun 5, 2016

  • Pip version:
  • Python version: 2.7.11
  • Operating System: Linux

Description:

The documentation on installation says the following:

pip is already installed if you're using Python 2 >=2.7.9 or Python 3 >=3.4
downloaded from `python.org <https://www.python.org>`_, but you'll need to
:ref:`upgrade pip <Upgrading pip>`.

However, I believe this is wrong since the default configuration for ensurepip is "no".

./configure --help | less

tells me this:

  --with(out)-ensurepip=[=OPTION]
                          "install" or "upgrade" using bundled pip, default is
                          "no"

What I've run:

We should probably put a warning for those people installing from source that pip has to be manually activated before installation.

@dstufft
Copy link
Member

dstufft commented Jun 5, 2016

@ustun Maybe it needs to be reworded differently, it should be installed by default for people downloading the Windows/OS X isntallers from www.python.org-- but not building from source.

@pfmoore
Copy link
Member

pfmoore commented Jun 5, 2016

I've just clarified this - "pip is already installed if you're using Python 2 >=2.7.9 or Python 3 >=3.4
binaries downloaded..."

@ustun
Copy link
Author

ustun commented Jun 5, 2016

Thanks.

Maybe we should add the following as the last paragraph in the first section:

If you are building from source, you need to enable installation of pip via the configure flag by specifying `--with-ensurepip=install`

@dstufft
Copy link
Member

dstufft commented Mar 30, 2017

With the rewording that Paul added I'm going to go ahead and close this issue. Documentation about building Python should likely go in the Python documentation, but we'd happily to consider PRs that add additional clarification. However I don't believe a tracking issue adds much value.

@dstufft dstufft closed this as completed Mar 30, 2017
@xavfernandez xavfernandez added the type: docs Documentation related label Mar 30, 2017
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation type: docs Documentation related
Projects
None yet
Development

No branches or pull requests

4 participants