PIP3-WHEEL(1)

📦
version 26.1.2 · 7 versions
, in ubuntu stonking

💅 PIP3-WHEEL — okay so, the pip3 wheel command, explained 💅

hey bestie!! you just opened the manual page for pip3-wheel — that's the wheel command from pip (you know, the one that lives in your venv and judges you when you forget --upgrade). sit down, grab a strawberry 🍓, and let's get into it.

✨ NAME ✨

pip3-wheel — it's literally the description of the pip3 wheel command. that's the whole vibe. that's the assignment. 💫

🎀 DESCRIPTION 🎀

okay so here's the tea: pip3 wheel builds Wheel archives for your requirements and your dependencies. you point it at stuff you want, it hands you wheels. iconic behavior honestly.

a Wheel is a built-package format, and the way it slays is that it means you don't have to recompile your software every single time you install it. no recompiling, no crying, no waiting. it's giving self-care. 😌✨

want more deets? the wheel docs are right here, go be nosy:

https://wheel.readthedocs.io/en/latest/

and heads up, pip wheel uses the build system interface as described here:

https://pip.pypa.io/en/stable/reference/build-system/
💡 lowkey important: those two links are the actual documentation references, so if you want the full lore, go read them. i'm just here to hype you up.

🌈 USAGE 🌈

this is how you actually run it. every one of these is a real, valid shape — copy away, bestie:

python -m pip wheel [options] <requirement specifier> ...
python -m pip wheel [options] -r <requirements file> ...
python -m pip wheel [options] [-e] <vcs project url> ...
python -m pip wheel [options] [-e] <local project path> ...
python -m pip wheel [options] <archive url/path> ...

so basically: options first, then whatever you're feeding it — a requirement specifier, a requirements file with -r, a VCS project URL, a local project path, or an archive url/path. pick your fighter. 🔥

👑 OPTIONS 👑

this is the part where i list every single flag because i would never gatekeep. no cap. 💜

  • -w, --wheel-dir <dir> — build those wheels into <dir>. the default is the current working directory (yes, wherever you're standing right now, that's where the wheels land). (environment variable: PIP_WHEEL_DIR)
  • --no-build-isolation — disables isolation when building a modern source distribution. 😭 careful though: if you use this, the build dependencies specified by PEP 518 must already be installed. no isolation, no safety net, you're on your own fr fr. (environment variable: PIP_NO_BUILD_ISOLATION)
  • --check-build-dependencies — checks the build dependencies. that's it, that's the job. ✅ (environment variable: PIP_CHECK_BUILD_DEPENDENCIES)
  • -c, --constraint <file> — constrain versions using the given constraints file. and yes, you can use this option multiple times — stack 'em, bestie. 🫶 (environment variable: PIP_CONSTRAINT)
  • --build-constraint <file> — constrain your build dependencies using the given constraints file. also can be used multiple times. 🎀 (environment variable: PIP_BUILD_CONSTRAINT)
  • -e, --editable <path/url> — install a project in editable mode (i.e. setuptools "develop mode") from a local project path or a VCS url. the classic "i'm still writing this so don't you dare freeze it" move. 💅 (environment variable: PIP_EDITABLE)
  • -r, --requirement <file> — install from the given requirements file. the file or URL can be in pip's requirements.txt format, or pylock.toml format. 🚨 heads up: pylock.toml support is experimental. also, this option can be used multiple times. (environment variable: PIP_REQUIREMENT)
  • --requirements-from-script <file> — install the dependencies of the given script file, as defined by PEP 723 inline metadata. yes, the deps live inside the script. it's giving ✨multitasking✨. (environment variable: PIP_REQUIREMENTS_FROM_SCRIPT)
  • --src <dir> — the directory to check out editable projects into. default in a virtualenv is <venv path>/src. default for global installs is <current dir>/src. 🧚 (environment variable: PIP_SRC, PIP_SOURCE, PIP_SOURCE_DIR, PIP_SOURCE_DIRECTORY)
  • --ignore-requires-python — ignore the Requires-Python information. you're overriding the vibes check, not my business. 🙈 (environment variable: PIP_IGNORE_REQUIRES_PYTHON)
  • --no-deps — don't install package dependencies. just the main character, no entourage. 👑 (environment variable: PIP_NO_DEPS, PIP_NO_DEPENDENCIES)
  • --progress-bar <progress_bar> — specify whether the progress bar should be used. in 'auto' mode, --quiet will suppress all progress bars. the options are [auto, on, off, raw], and the default is auto. 🦋 (environment variable: PIP_PROGRESS_BAR)
  • --no-verify — don't verify if the built wheel is valid. it's giving "i trust myself" energy. 💀 (environment variable: PIP_NO_VERIFY)
  • -C, --config-settings <settings> — configuration settings to be passed to the build backend. settings take the form KEY=VALUE. use multiple --config-settings options to pass multiple keys to the backend. 🔧 (environment variable: PIP_CONFIG_SETTINGS)
  • --require-hashes — require a hash to check each requirement against, for repeatable installs. and note: this option is implied when any package in a requirements file has a --hash option. so it might just show up uninvited. 😭 (environment variable: PIP_REQUIRE_HASHES)
  • --group <[path:]group> — install a named dependency-group from a "pyproject.toml" file. if a path is given, the name of the file must be "pyproject.toml". it defaults to using "pyproject.toml" in the current directory. 🌸 (environment variable: PIP_GROUP)
  • --no-clean — don't clean up build directories. leaving a little mess behind, we love a chaotic queen. 🎀 (environment variable: PIP_NO_CLEAN)

💖 Author 💖

pip developers — the whole squad, collectively responsible for all of this. 👑

The pip developers — yes, the same people. they own it, they wrote it, they keep it. 💜

and that's the whole page bestie!! this was pip3-wheel, from version 26.1, dated Jun 02, 2026 (which is the manual's own footer magic, not me making things up ✨). now go build some wheels and absolutely ate. 🦋🌈⭐

bye bye, mwah 💅

📦 where this page comes from