This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Axel
Recipients Axel, docs@python
Date 2016-03-29.14:24:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1459261486.77.0.745706792357.issue26665@psf.upfronthosting.co.za>
In-reply-to
Content
Relevant page:

    https://docs.python.org/2/library/ensurepip.html

One may read:

    In most cases, end users of Python shouldn’t need to invoke
    this module directly (as pip should be bootstrapped by default),
    but it may be needed if installing pip was skipped when
    installing Python (or when creating a virtual environment) or
    after explicitly uninstalling pip.

As far as I correctly read the configure file that comes with the 2.7.11 tarball, the default is to behave as if --with-ensurepip=no had been passed.

As a result, that sentence fragment:

    (as pip should be bootstrapped by default)

may appear somewhat ambiguous for those compiling Python themselves.

Perhaps could this one avoid some head scratching:

    (as packagers are expected to have bootstrapped pip)

HTH,
Axel
History
Date User Action Args
2016-03-29 14:24:46Axelsetrecipients: + Axel, docs@python
2016-03-29 14:24:46Axelsetmessageid: <1459261486.77.0.745706792357.issue26665@psf.upfronthosting.co.za>
2016-03-29 14:24:46Axellinkissue26665 messages
2016-03-29 14:24:46Axelcreate