PYSIDE6-DEPLOY(1)

💖 PYSIDE6-DEPLOY(1) 💖

okay bestie, welcome to the pyside6-deploy page — it lives in the PySide6 tools section of the manual, and honestly? it's giving "ship your app to the world" energy. 🚀

---

✨ NAME ✨

pyside6-deploy — deploy 🫶

---

🌈 DESCRIPTION 🌈

so basically, here's the vibe. the usage line goes like this, and yes it's long, she's a main character:

deploy.py [-h] [-c CONFIG_FILE] [--init] [-v] [--dry-run]
          [--keep-deployment-files] [-f] [--name NAME] [--extra-ignore-dirs
          EXTRA_IGNORE_DIRS] [--extra-modules EXTRA_MODULES] [--mode
          {onefile,standalone}] [--nuitka-version NUITKA_VERSION] [main_file]

this tool deploys PySide6 to desktop platforms — that's Windows, Linux and macOS, the whole trio 👑. and depending on which platform you're on, it produces a different lil executable baby:

• Windows → .exe
• macOS → .app
• Linux → .bin

slay. no cap. literally each platform gets its own flavor. ✨

---

🎀 positional arguments 🎀

• main_file — the path to your main python file, aka where the magic starts 💅

---

🦋 options 🦋

okay this is the part you actually came for, so let's go one by one, no skipping, we respect every single flag in this house:

• -h, --help — shows you this help message and then dips out (exit). the classic. 🙈
• -c, --config-file CONFIG_FILE — the path to your .spec config file 📄
• --init — creates the pysidedeploy.spec file for you, but only if it doesn't already exist. no overwriting, she respects boundaries 💖
• -v, --verbose — run it in verbose mode, aka it tells you everything that's happening 🗣️
• --dry-run — just shows you the commands that would be run. peek behind the curtain, touch nothing ✨
• --keep-deployment-files — keeps the generated deployment files that were generated 👑
• -f, --force — forces all input prompts. she will not be asking twice 💅
• --name NAME — your application's name 🏷️
• --extra-ignore-dirs EXTRA_IGNORE_DIRS — a comma-separated list of directory names inside your project dir. these directories get skipped when it's searching for Python files that are relevant to the project. example usage: --extra-ignore-dirs=doc,translations
• --extra-modules EXTRA_MODULES — a comma-separated list of Qt modules to add to the application, in case they don't get found automatically. this whole situation happens when you've got 'import PySide6' in your code instead of 'from PySide6 import <module>' (iykyk 😭). the module name is specified either by omitting the prefix of Qt or by including it. example usage 1: --extramodules=Network,Svg example usage 2: --extramodules=QtNetwork,QtSvg
• --mode {onefile,standalone} — the mode your application gets deployed in. the options are onefile and standalone, and the default value is onefile. this option translates to the mode Nuitka uses to create the executable. heads up though: macOS by default uses the --standalone option. 🌸
• --nuitka-version NUITKA_VERSION — overrides the Nuitka version that gets installed for deployment, e.g. --nuitka-version=4.0 🔥

reminder bestie: those are the only values for --mode (onefile and standalone), and the default is onefile — except on macOS where --standalone is the default. don't come for me, that's just what the page says 💜

---

aaaand that's the whole thing!! you're officially a deployment girly now 🧚🍓

this page comes from pyside6-deploy 6.11, dated September 2026 — so when future you is reading this in a group chat, you know exactly which version ate 💅✨ periodt.