Text of peps.python.org › pep-0453 as Styx crawled it on Nov 20, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

PEP 453 – Explicit bootstrapping of pip in Python installations | peps.python.org

PEP 453 – Explicit bootstrapping of pip in Python installations PEP 453 – Explicit bootstrapping of pip in Python installations Author : Donald Stufft <donald at stufft.io>, Alyssa Coghlan <ncoghlan at gmail.com> BDFL-Delegate : Martin von Löwis Status : Final Type : Standards Track Created : 10-Aug-2013 Post-History : 30-Aug-2013, 15-Sep-2013, 18-Sep-2013, 19-Sep-2013, 23-Sep-2013, 29-Sep-2013, 13-Oct-2013, 20-Oct-2013 Resolution : Python-Dev message Table of Contents Abstract PEP Acceptance Rationale Improving the new user experience Enabling the evolution of the broader Python packaging ecosystem Why pip?

Proposal Overview Explicit bootstrapping mechanism Security considerations Reliability considerations Implementation strategy Integration timeline Proposed CLI Proposed module API Invocation from the CPython installers Installing from source Changes to virtual environments Documentation Bundling CA certificates with CPython Automatic installation of setuptools Updating the private copy of pip Updating the ensurepip module API and CLI Uninstallation Script Execution on Windows Recommendations for Downstream Distributors Policies & Governance Backwards Compatibility Security Releases Licensing Appendix: Rejected Proposals Changing the name of the scripts directory on Windows Including ensurepip in Python 2.7, and 3.3 Automatically contacting PyPI when bootstrapping pip Implicit bootstrap Including pip directly in the standard library Defaulting to –user installation References Copyright Abstract This PEP proposes that the Installing Python Modules guide in Python 2.7, 3.3 and 3.4 be updated to officially recommend the use of pip as the default installer for Python packages, and that appropriate technical changes be made in Python 3.4 to provide pip by default in support of that recommendation.

PEP Acceptance This PEP was accepted for inclusion in Python 3.4 by Martin von Löwis on Tuesday 22nd October, 2013. Issue 19347 has been created to track the implementation of this PEP. Rationale There are two related, but distinct rationales for the proposal in this PEP. The first relates to the experience of new users, while the second relates to better enabling the evolution of the broader Python packaging ecosystem.

Improving the new user experience Currently, on systems without a platform package manager and repository, installing a third-party Python package into a freshly installed Python requires first identifying an appropriate package manager and then installing it. Even on systems that do have a platform package manager, it is unlikely to include every package that is available on the Python Package Index, and even when a desired third-party package is available, the correct name in the platform package manager may not be clear.

This means that, to work effectively with the Python Package Index ecosystem, users must know which package manager to install, where to get it, and how to install it. The effect of this is that third-party Python projects are currently required to choose from a variety of undesirable alternatives: Assume the user already has a suitable cross-platform package manager installed. Duplicate the instructions and tell their users how to install the package manager.

Completely forgo the use of dependencies to ease installation concerns for their users. All of these available options have significant drawbacks. If a project simply assumes a user already has the tooling then beginning users may get a confusing error message when the installation command doesn’t work. Some operating systems may ease this pain by providing a global hook that looks for commands that don’t exist and suggest an OS package they can install to make the command work, but that only works on systems with platform package managers that include a package that provides the relevant cross-platform installer command (such as many major Linux distributions).

No such assistance is available for Windows and Mac OS X users, or more conservative Linux distributions. The challenges of dealing with this problem for beginners (who are often also completely new to programming, the use of command line tools and editing system environment variables) are a regular feature of feedback the core Python developers receive from professional educators and others introducing new users to Python.

If a project chooses to duplicate the installation instructions and tell their users how to install the package manager before telling them how to install their own project then whenever these instructions need updates they need updating by every project that has duplicated them. This is particular problematic when there are multiple competing installation tools available, and different projects recommend different tools.

This specific problem can be partially alleviated by strongly promoting pip as the default installer and recommending that other projects reference pip’s own bootstrapping instructions rather than duplicating them. However the user experience created by this approach still isn’t particularly good (although there is an effort under way to create a combined Windows installer for pip and its dependencies that should improve matters on that platform, and Mac OS X and *nix platforms generally have wget and hence the ability to easily download and run the bootstrap scripts from the command line).

The projects that have decided to forgo dependencies altogether are forced to either duplicate the efforts of other projects by inventing their own solutions to problems or are required to simply include the other projects in their own source trees. Both of these options present their own problems either in duplicating maintenance work across the ecosystem or potentially leaving users vulnerable to security issues because the included code or duplicated efforts are not automatically updated when upstream releases a new version.

By officially recommending and providing by default a specific cross-platform package manager it will be easier for users trying to install these third-party packages as well as easier for the people distributing them as they should now be able to safely assume that most users will have the appropriate installation tools available (or access to clear instructions on how to obtain them). This is expected to become more important in the future as the Wheel package format (deliberately) does not have a built in “installer” in the form of setup.py so users wishing to install from a wheel file will want an installer even in the simplest cases.

Reducing the burden of actually installing a third-party package should also decrease the pressure to add every useful module to the standard library. This will allow additions to the standard library to focus more on why Python should have a particular tool out of the box, and why it is reasonable for that package to adopt the standard library’s 18-24 month feature release cycle, instead of using the general difficulty of installing third-party packages as justification for inclusion.

Providing a standard installation system also helps with bootstrapping alternate build and installer systems, such as zc.buildout , hashdist and conda . So long as pip install <tool> works, then a standard Python-specific installer provides a reasonably secure, cross platform mechanism to get access to these utilities. Enabling the evolution of the broader Python packaging ecosystem As no new packaging standard can achieve widespread adoption without a transition strategy that covers the versions of Python that are in widespread current use (rather than merely future versions, like most language features), the change proposed in this PEP is considered a necessary step in the evolution of the Python packaging ecosystem The broader community has embraced the Python Package Index as a mechanism for distributing and installing Python software, but the different concerns of language evolution and secure software distribution mea

The rest of this page is on the live site.