This is the overall tracking issue for the implementation of PEP-453. The following subtasks will be created as separate issues:

• update the Installing Python Modules documentation to reference www.pip-installer.org in Python 2.7, 3.3 and 3.4 (ncoghlan)
• initial implementation of ensurepip (dstufft)
• Python 3.4 documentation updates for ensurepip (dstufft and/or ncoghlan)
• Windows installer updates, including PATH manipulation updates (MvL?)
• Mac OS X installer updates (Ned?)
• venv and pyvenv updates (dstufft? TBC)

One more task to track - updating to the latest upstream pip before beta 2.

venv shouldn't need any changes. The pyvenvex.py [1] script I posted to distutils-sig installs setuptools and pip into venvs, and it can be used to update pyvenv (where AFAICT changes are only required to change where the pip to be installed comes from).

[1] https://gist.github.com/vsajip/4673395

Check PEP-453 again: http://www.python.org/dev/peps/pep-0453/#changes-to-virtual-environments

Rather than only changing pyvenv, the API in the PEP is to add "with_pip" parameters to the venv module API, so that anyone building pyvenv style tools on top of venv can easily request installation of pip by passing "with_pip=True". The change to pyvenv is then to just add the --without-pip flag (since the default is inverted for the two interfaces - library API is opt-in for backwards compatibility, tool CLI is opt-out)

Just clarifying how I plan to track this: as we start specific tasks, we'll
create new issues and make this one depend on them. That seems better to me
than creating a whole raft of issues up front that are then depending on
each other.

First two working issues created:

bpo-19406 for the addition of ensurepip and its docs
bpo-19407 for the Installing Python Modules updates

New subtasks:

bpo-19550: Windows installer integration
bpo-19551: Mac OS X installer integration
bpo-19552: venv module and pyvenv integration
bpo-19553: "make install" and "make altinstall" integration open

bpo-19693 covers an anomaly where "make altinstall && make install" doesn't quite do the same thing as "make install" (the "pip3" script will be missing in the former case)

bpo-19694 is a new issue for one of the buildbots objecting to the new venv tests.

Created bpo-19728 to track what is needed before the installation of pip can be made the default in the installers (at least for Windows, but I assume MvL's concerns would apply equally to the Mac OS X installer)

bpo-19744 covers better handling of the case where SSL/TLS support is not available in the current Python.

bpo-19734 covers the fact that pip environment variable settings impact venv and ensurepip

bpo-19766 covers the fact that the vendored urllib3 needs to be updated in order to handle the case where Python is built without threading support.

Upgrading to release blocker status, since we'd prefer to have everything we can sorted before beta 2

bpo-20053 covers the fact that the default pip config file affects ensurepip and venv.

I propose to downgrade this from "release blocker" again. "prefer to have everything we can sorted" is IMO not a sufficient rationale to block the release; if taken literally, 3.4 could never ever release since it doesn't have everything sorted out that I would personally want to sort out some time in Python.

If individual subissues should block the release, the should be promoted.

Agreed, it was mostly to ensure we reviewed the status to make sure we were
happy with progress. The only remaining "must fix" item is the docs update,
and that's shouldn't block beta 2 (although I'll still try to get at least
an initial version done now that pip 1.5 is released).

Actually, with the docs update being the only remaining "this really should be done before 3.4 is released" issue related to PEP-453, I think this tracking issue has now served its purpose.

So, closing this umbrella issue now, since bpo-19407 covers the docs update.

Thanks again to everyone that contributed the various bits and pieces needed to make the PEP a reality :)