get-pip.py
is a bootstrapping script that enables users to install pip
in Python environments that don't already have it installed. You
should not directly reference the files located in this repository and instead
use the versions located at https://bootstrap.pypa.io/.
$ curl -sSL https://bootstrap.pypa.io/get-pip.py -o get-pip.py
$ python get-pip.py
Upon execution, get-pip.py
will install the latest version of pip
into the
current Python environment. When using Python 3.11 or older, by default the
packages setuptools
and wheel
will also be installed if an existing version
of them was not found.
It is possible to provide additional arguments to the underlying script. These
are passed through to the underlying pip install
command, and can thus be
used to constrain the versions of the packages, install additional packages,
or to pass other pip options such as --no-index
.
# Constrain the pip version
$ python get-pip.py "pip < 21.0"
# Force the installation of `setuptools` and `wheel` on newer Python versions.
$ python get-pip.py setuptools wheel
# Install packages from a local directory instead of PyPI.
$ python get-pip.py --no-index --find-links=/local/copies
This script also has its own options, which control which packages it will install.
--no-setuptools
: Do not attempt to installsetuptools
. This is a no-op on Python 3.12+.--no-wheel
: Do not attempt to installwheel
. This is a no-op on Python 3.12+.
You need to have a nox
available on the CLI.
get-pip.py
bundles a copy of pip with a tiny amount of glue code. This glue
code comes from the templates/
directory.
If you just made a pip release, run nox -s update-for-release -- <version>
.
This session will handle all the script updates (by running generate
), commit
the changes and tag the commit.
IMPORTANT: Check that the correct files got modified before pushing. The session will pause to let you do this.
Run nox -s generate
.
If you run into bugs, you can file them in our issue tracker.
You can also join #pypa
or #pypa-dev
on Freenode to ask questions or
get involved.
Everyone interacting in the get-pip project's codebases, issue trackers, chat rooms, and mailing lists is expected to follow the PSF Code of Conduct.