PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB` .. _`pip wheel`: pip wheel --------- .. contents:: Usage ***** .. pip-command-usage:: wheel Description *********** .. pip-command-description:: wheel Build System Interface ++++++++++++++++++++++ In order for pip to build a wheel, ``setup.py`` must implement the ``bdist_wheel`` command with the following syntax:: python setup.py bdist_wheel -d TARGET This command must create a wheel compatible with the invoking Python interpreter, and save that wheel in the directory TARGET. No other build system commands are invoked by the ``pip wheel`` command. Customising the build ~~~~~~~~~~~~~~~~~~~~~ It is possible using ``--global-option`` to include additional build commands with their arguments in the ``setup.py`` command. This is currently the only way to influence the building of C extensions from the command line. For example:: pip wheel --global-option bdist_ext --global-option -DFOO wheel will result in a build command of :: setup.py bdist_ext -DFOO bdist_wheel -d TARGET which passes a preprocessor symbol to the extension build. Such usage is considered highly build-system specific and more an accident of the current implementation than a supported interface. Options ******* .. pip-command-options:: wheel .. pip-index-options:: Examples ******** 1. Build wheels for a requirement (and all its dependencies), and then install :: $ pip wheel --wheel-dir=/tmp/wheelhouse SomePackage $ pip install --no-index --find-links=/tmp/wheelhouse SomePackage