[{"data":1,"prerenderedAt":1218},["ShallowReactive",2],{"page-\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fnuitka-vs-pyinstaller-for-python-clis\u002F":3,"content-directory":671},{"id":4,"title":5,"body":6,"date":656,"description":657,"difficulty":658,"draft":659,"extension":660,"meta":661,"navigation":163,"path":662,"seo":663,"stem":664,"tags":665,"updated":656,"__hash__":670},"content\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fnuitka-vs-pyinstaller-for-python-clis\u002Findex.md","Nuitka vs PyInstaller for Python CLI Binaries",{"type":7,"value":8,"toc":639},"minimark",[9,28,33,55,59,68,73,77,81,84,87,93,104,110,116,120,123,191,196,277,282,360,386,397,401,404,407,420,424,477,481,488,553,559,563,566,570,575,578,582,588,592,595,599,602,606,635],[10,11,12,13,17,18,21,22,27],"p",{},"You need to give a Python CLI to people who do not have Python — or who should not have to care which Python they have. A standalone binary solves it: one file (or one folder) that runs on a machine with no interpreter installed. Two tools dominate. ",[14,15,16],"strong",{},"PyInstaller"," bundles your bytecode, its dependencies and a copy of the Python interpreter into an executable. ",[14,19,20],{},"Nuitka"," compiles your Python to C, builds it with a C compiler, and links it against the Python runtime. Both produce binaries that run without Python; they differ in build time and toolchain requirements, in how easily the result can be inspected, and sometimes in startup performance. This guide compares them for command-line tools specifically, shows a working build with each, and gives a way to decide based on measurements rather than folklore. It belongs to the ",[23,24,26],"a",{"href":25},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002F","distributing CLIs as standalone binaries topic",".",[29,30,32],"h2",{"id":31},"prerequisites","Prerequisites",[34,35,36,45,48],"ul",{},[37,38,39,40,44],"li",{},"A CLI with a single entry function, packaged normally (see ",[23,41,43],{"href":42},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fwriting-pyproject-toml-metadata-for-a-cli\u002F","writing pyproject.toml metadata for a CLI",").",[37,46,47],{},"For Nuitka, a C compiler: gcc or clang on Linux and macOS, MSVC (or MinGW, which Nuitka can download) on Windows.",[37,49,50,51,27],{},"Builds happen per platform — neither tool cross-compiles — so you need a Linux, macOS and Windows machine or CI runner for each target. The CI matrix is in ",[23,52,54],{"href":53},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbuilding-cross-platform-release-binaries-in-ci\u002F","building cross-platform release binaries in CI",[29,56,58],{"id":57},"how-each-tool-works","How each tool works",[10,60,61,63,64,27],{},[14,62,16],{}," analyses your imports, collects the bytecode of every module it finds plus the shared libraries they need, and packs them with a bootloader and a copy of the Python runtime. In one-folder mode the result is a directory with an executable and its libraries; in one-file mode that directory is appended to the executable and extracted to a temporary location on each run. The detailed walkthrough is in ",[23,65,67],{"href":66},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbundling-a-python-cli-with-pyinstaller\u002F","bundling a Python CLI with PyInstaller",[10,69,70,72],{},[14,71,20],{}," translates each Python module into C code that performs the same operations through the CPython API, compiles that C with a real compiler, and links it into an executable. Standard-library and third-party modules are compiled too (or included as bytecode where compilation is not possible). Standalone mode produces a folder; onefile mode packs that folder into a single self-extracting executable, similar in shape to PyInstaller's.",[74,75],"inline-diagram",{"name":76},"nk-pipeline",[29,78,80],{"id":79},"side-by-side","Side by side",[74,82],{"name":83},"nk-compare",[10,85,86],{},"A few points deserve expansion.",[10,88,89,92],{},[14,90,91],{},"Build time and toolchain."," PyInstaller builds a typical CLI in well under a minute with nothing but Python. Nuitka builds take several minutes — sometimes much longer for large dependency trees — and need a working C compiler on every build machine. In CI that is manageable; on developers' laptops, especially Windows ones, it is a real cost.",[10,94,95,98,99,103],{},[14,96,97],{},"Startup."," Both onefile modes pay to unpack their payload to a temporary directory on every start, which dominates startup for small tools. Nuitka can cache the unpacked files between runs (",[100,101,102],"code",{},"--onefile-tempdir-spec"," pointing at a cache directory), which removes most of that cost; PyInstaller's one-folder mode avoids unpacking entirely. For compiled code itself, Nuitka is often somewhat faster, but CLIs usually spend their time importing and waiting on I\u002FO, so measure your own tool rather than assuming.",[10,105,106,109],{},[14,107,108],{},"Inspectability."," A PyInstaller binary contains bytecode that tools can extract and decompile with little effort. Nuitka's output is compiled C, which is considerably harder to reverse-engineer. Neither is protection for secrets — never embed credentials in any binary — but if you distribute a commercial tool and would rather its source not be trivially readable, Nuitka raises the bar.",[10,111,112,115],{},[14,113,114],{},"Compatibility."," Both handle most pure-Python dependencies automatically, and both need hints for code that imports modules dynamically — plugin systems via entry points, lazy-loaded subcommands, packages that locate data files at runtime. The hints differ in syntax but not in kind.",[29,117,119],{"id":118},"the-recipe-the-same-cli-both-ways","The recipe: the same CLI, both ways",[10,121,122],{},"A tiny launcher module gives both tools a script to start from, so the build does not depend on how your package is installed:",[124,125,130],"pre",{"className":126,"code":127,"language":128,"meta":129,"style":129},"language-python shiki shiki-themes github-light github-dark","# packaging\u002Flauncher.py\nfrom mytool.cli import app\n\nif __name__ == \"__main__\":\n    app()\n","python","",[100,131,132,141,158,165,185],{"__ignoreMap":129},[133,134,137],"span",{"class":135,"line":136},"line",1,[133,138,140],{"class":139},"sJ8bj","# packaging\u002Flauncher.py\n",[133,142,144,148,152,155],{"class":135,"line":143},2,[133,145,147],{"class":146},"szBVR","from",[133,149,151],{"class":150},"sVt8B"," mytool.cli ",[133,153,154],{"class":146},"import",[133,156,157],{"class":150}," app\n",[133,159,161],{"class":135,"line":160},3,[133,162,164],{"emptyLinePlaceholder":163},true,"\n",[133,166,168,171,175,178,182],{"class":135,"line":167},4,[133,169,170],{"class":146},"if",[133,172,174],{"class":173},"sj4cs"," __name__",[133,176,177],{"class":146}," ==",[133,179,181],{"class":180},"sZZnC"," \"__main__\"",[133,183,184],{"class":150},":\n",[133,186,188],{"class":135,"line":187},5,[133,189,190],{"class":150},"    app()\n",[10,192,193],{},[14,194,195],{},"PyInstaller:",[124,197,201],{"className":198,"code":199,"language":200,"meta":129,"style":129},"language-bash shiki shiki-themes github-light github-dark","uv run --with pyinstaller pyinstaller packaging\u002Flauncher.py \\\n  --name mytool --onefile --console \\\n  --collect-data mytool \\\n  --hidden-import mytool.commands.deploy \\\n  --hidden-import mytool.commands.report\n.\u002Fdist\u002Fmytool --version\n","bash",[100,202,203,226,242,251,261,268],{"__ignoreMap":129},[133,204,205,209,212,215,218,220,223],{"class":135,"line":136},[133,206,208],{"class":207},"sScJk","uv",[133,210,211],{"class":180}," run",[133,213,214],{"class":173}," --with",[133,216,217],{"class":180}," pyinstaller",[133,219,217],{"class":180},[133,221,222],{"class":180}," packaging\u002Flauncher.py",[133,224,225],{"class":173}," \\\n",[133,227,228,231,234,237,240],{"class":135,"line":143},[133,229,230],{"class":173},"  --name",[133,232,233],{"class":180}," mytool",[133,235,236],{"class":173}," --onefile",[133,238,239],{"class":173}," --console",[133,241,225],{"class":173},[133,243,244,247,249],{"class":135,"line":160},[133,245,246],{"class":173},"  --collect-data",[133,248,233],{"class":180},[133,250,225],{"class":173},[133,252,253,256,259],{"class":135,"line":167},[133,254,255],{"class":173},"  --hidden-import",[133,257,258],{"class":180}," mytool.commands.deploy",[133,260,225],{"class":173},[133,262,263,265],{"class":135,"line":187},[133,264,255],{"class":173},[133,266,267],{"class":180}," mytool.commands.report\n",[133,269,271,274],{"class":135,"line":270},6,[133,272,273],{"class":207},".\u002Fdist\u002Fmytool",[133,275,276],{"class":173}," --version\n",[10,278,279],{},[14,280,281],{},"Nuitka:",[124,283,285],{"className":198,"code":284,"language":200,"meta":129,"style":129},"uv run --with nuitka python -m nuitka packaging\u002Flauncher.py \\\n  --onefile --output-filename=mytool --output-dir=build \\\n  --include-package=mytool \\\n  --include-package-data=mytool \\\n  --onefile-tempdir-spec=\"{CACHE_DIR}\u002Fmytool\u002F{VERSION}\" \\\n  --assume-yes-for-downloads\n.\u002Fbuild\u002Fmytool --version\n",[100,286,287,310,323,330,337,347,352],{"__ignoreMap":129},[133,288,289,291,293,295,298,301,304,306,308],{"class":135,"line":136},[133,290,208],{"class":207},[133,292,211],{"class":180},[133,294,214],{"class":173},[133,296,297],{"class":180}," nuitka",[133,299,300],{"class":180}," python",[133,302,303],{"class":173}," -m",[133,305,297],{"class":180},[133,307,222],{"class":180},[133,309,225],{"class":173},[133,311,312,315,318,321],{"class":135,"line":143},[133,313,314],{"class":173},"  --onefile",[133,316,317],{"class":173}," --output-filename=mytool",[133,319,320],{"class":173}," --output-dir=build",[133,322,225],{"class":173},[133,324,325,328],{"class":135,"line":160},[133,326,327],{"class":173},"  --include-package=mytool",[133,329,225],{"class":173},[133,331,332,335],{"class":135,"line":167},[133,333,334],{"class":173},"  --include-package-data=mytool",[133,336,225],{"class":173},[133,338,339,342,345],{"class":135,"line":187},[133,340,341],{"class":173},"  --onefile-tempdir-spec=",[133,343,344],{"class":180},"\"{CACHE_DIR}\u002Fmytool\u002F{VERSION}\"",[133,346,225],{"class":173},[133,348,349],{"class":135,"line":270},[133,350,351],{"class":173},"  --assume-yes-for-downloads\n",[133,353,355,358],{"class":135,"line":354},7,[133,356,357],{"class":207},".\u002Fbuild\u002Fmytool",[133,359,276],{"class":173},[10,361,362,363,366,367,370,371,375,376,366,379,382,383,385],{},"The flags map onto each other: ",[100,364,365],{},"--collect-data"," \u002F ",[100,368,369],{},"--include-package-data"," bundle templates and other package files loaded with ",[23,372,374],{"href":373},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbundling-data-files-with-importlib-resources\u002F","importlib.resources","; ",[100,377,378],{},"--hidden-import",[100,380,381],{},"--include-package"," make sure lazily imported command modules are included even though no static import reaches them. Nuitka's ",[100,384,102],{}," with a cache path keeps the unpacked files between runs, trading a little disk space for much faster starts.",[10,387,388,389,392,393,396],{},"Plugins discovered through entry points need extra care with both tools: the plugin packages must be bundled explicitly, and their distribution metadata (which holds the entry points) must be included — ",[100,390,391],{},"--copy-metadata"," in PyInstaller, ",[100,394,395],{},"--include-distribution-metadata"," in Nuitka.",[29,398,400],{"id":399},"choosing","Choosing",[74,402],{"name":403},"nk-decision",[10,405,406],{},"Start with PyInstaller. It is quick to adopt, builds fast, needs no compiler, and has years of accumulated hooks for popular libraries. Move to Nuitka when you have a concrete reason: measured startup or runtime gains that matter to your users, a wish to make the shipped code harder to inspect, or trouble with a library that Nuitka happens to handle better. Keep the decision reversible by keeping build configuration in one script per tool and the launcher module shared between them.",[10,408,409,410,414,415,419],{},"Also consider whether you need a binary at all. If your users have Python, ",[23,411,413],{"href":412},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-tool-install-vs-pipx-for-clis\u002F","installing with pipx or uv tool"," is simpler for everyone, and a ",[23,416,418],{"href":417},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fshipping-a-cli-as-a-zipapp-with-shiv\u002F","zipapp built with shiv"," gives single-file distribution without freezing the interpreter.",[29,421,423],{"id":422},"ux-considerations","UX considerations",[34,425,426,436,457,463],{},[37,427,428,431,432,435],{},[14,429,430],{},"Ship one-folder builds where you can."," Package managers (Homebrew, Scoop, ",[100,433,434],{},".deb",") install folders happily, and one-folder builds start fastest because nothing is unpacked. Keep onefile for \"download and run\" distribution.",[37,437,438,449,450,452,453,27],{},[14,439,440,441,444,445,448],{},"Keep ",[100,442,443],{},"--version"," and ",[100,446,447],{},"doctor"," working in the binary."," They are how users and you confirm what they are running; see the ",[100,451,447],{}," command in ",[23,454,456],{"href":455},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fsmoke-testing-the-built-wheel-in-ci\u002F","smoke-testing the built wheel in CI",[37,458,459,462],{},[14,460,461],{},"Sign and notarise on macOS and Windows."," Unsigned binaries trigger Gatekeeper and SmartScreen warnings that make users distrust a perfectly good tool. Both tools produce binaries that can be signed with the platform's standard tooling.",[37,464,465,468,469,472,473,476],{},[14,466,467],{},"Watch temp directories."," Onefile binaries extract to temporary space; systems that mount ",[100,470,471],{},"\u002Ftmp"," with ",[100,474,475],{},"noexec"," break them. Document the environment variable or option that moves extraction elsewhere.",[29,478,480],{"id":479},"testing-the-behaviour","Testing the behaviour",[10,482,483,484,487],{},"Test the binary, not the source, on a machine or runner ",[14,485,486],{},"without Python",", and measure startup so the comparison between tools is grounded:",[124,489,491],{"className":198,"code":490,"language":200,"meta":129,"style":129},"# Functional smoke test of the frozen binary\n.\u002Fdist\u002Fmytool --version\n.\u002Fdist\u002Fmytool doctor                      # imports every lazy command, loads every resource\n.\u002Fdist\u002Fmytool --help > \u002Fdev\u002Fnull\n\n# Startup, measured rather than guessed (install hyperfine separately)\nhyperfine --warmup 3 '.\u002Fdist\u002Fmytool --version' '.\u002Fbuild\u002Fmytool --version'\n",[100,492,493,498,504,514,527,531,536],{"__ignoreMap":129},[133,494,495],{"class":135,"line":136},[133,496,497],{"class":139},"# Functional smoke test of the frozen binary\n",[133,499,500,502],{"class":135,"line":143},[133,501,273],{"class":207},[133,503,276],{"class":173},[133,505,506,508,511],{"class":135,"line":160},[133,507,273],{"class":207},[133,509,510],{"class":180}," doctor",[133,512,513],{"class":139},"                      # imports every lazy command, loads every resource\n",[133,515,516,518,521,524],{"class":135,"line":167},[133,517,273],{"class":207},[133,519,520],{"class":173}," --help",[133,522,523],{"class":146}," >",[133,525,526],{"class":180}," \u002Fdev\u002Fnull\n",[133,528,529],{"class":135,"line":187},[133,530,164],{"emptyLinePlaceholder":163},[133,532,533],{"class":135,"line":270},[133,534,535],{"class":139},"# Startup, measured rather than guessed (install hyperfine separately)\n",[133,537,538,541,544,547,550],{"class":135,"line":354},[133,539,540],{"class":207},"hyperfine",[133,542,543],{"class":173}," --warmup",[133,545,546],{"class":173}," 3",[133,548,549],{"class":180}," '.\u002Fdist\u002Fmytool --version'",[133,551,552],{"class":180}," '.\u002Fbuild\u002Fmytool --version'\n",[10,554,555,556,558],{},"The ",[100,557,447],{}," run is what catches missing hidden imports and data files — the failures unique to frozen builds, which appear only when a user reaches the command that needed the missing module. Run it in CI on each platform after building, and fail the release if it fails. For startup comparisons, run both binaries on the same machine several times; single measurements of onefile executables vary a lot with disk cache state.",[29,560,562],{"id":561},"conclusion","Conclusion",[10,564,565],{},"PyInstaller and Nuitka both turn a Python CLI into something users can run without Python. PyInstaller bundles bytecode and an interpreter quickly with no compiler; Nuitka compiles to C, taking longer and needing a toolchain, in exchange for output that is harder to inspect and sometimes faster. For most CLIs PyInstaller is the right default; switch when a measurement or a requirement says so. Either way, include lazy imports and package data explicitly, prefer one-folder builds for package managers, sign what you ship, and smoke-test the binary itself on every platform.",[29,567,569],{"id":568},"frequently-asked-questions","Frequently asked questions",[571,572,574],"h3",{"id":573},"can-i-build-a-linux-binary-on-macos-or-a-windows-binary-on-linux","Can I build a Linux binary on macOS, or a Windows binary on Linux?",[10,576,577],{},"No — neither tool cross-compiles. Build on each target platform, typically with a CI matrix of runners. For Linux, build on the oldest distribution you support, because binaries link against the system's C library and run on that version or newer.",[571,579,581],{"id":580},"why-is-my-onefile-binary-slow-to-start","Why is my onefile binary slow to start?",[10,583,584,585,587],{},"It extracts its contents to a temporary directory on every run. Use one-folder mode, or with Nuitka point ",[100,586,102],{}," at a cache directory so extraction happens once per version.",[571,589,591],{"id":590},"do-antivirus-tools-flag-these-binaries","Do antivirus tools flag these binaries?",[10,593,594],{},"Occasionally, especially PyInstaller onefile builds, because the bootloader pattern resembles some malware packers. Code signing reduces false positives substantially; submitting false positives to vendors fixes individual cases.",[571,596,598],{"id":597},"what-about-pyoxidizer-or-other-tools","What about PyOxidizer or other tools?",[10,600,601],{},"PyOxidizer is no longer actively developed. Briefcase targets application installers more than CLIs. For command-line tools today, PyInstaller and Nuitka are the practical choices, with shiv or plain zipapps when a Python interpreter is available.",[29,603,605],{"id":604},"related","Related",[34,607,608,614,619,624,629],{},[37,609,610,611],{},"Up: ",[23,612,613],{"href":25},"Distributing CLIs as standalone binaries",[37,615,616],{},[23,617,618],{"href":66},"Bundling a Python CLI with PyInstaller",[37,620,621],{},[23,622,623],{"href":53},"Building cross-platform release binaries in CI",[37,625,626],{},[23,627,628],{"href":417},"Shipping a CLI as a zipapp with shiv",[37,630,631],{},[23,632,634],{"href":633},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fhomebrew-and-scoop-packaging-for-python-clis\u002F","Homebrew and Scoop packaging for Python CLIs",[636,637,638],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}",{"title":129,"searchDepth":143,"depth":143,"links":640},[641,642,643,644,645,646,647,648,649,655],{"id":31,"depth":143,"text":32},{"id":57,"depth":143,"text":58},{"id":79,"depth":143,"text":80},{"id":118,"depth":143,"text":119},{"id":399,"depth":143,"text":400},{"id":422,"depth":143,"text":423},{"id":479,"depth":143,"text":480},{"id":561,"depth":143,"text":562},{"id":568,"depth":143,"text":569,"children":650},[651,652,653,654],{"id":573,"depth":160,"text":574},{"id":580,"depth":160,"text":581},{"id":590,"depth":160,"text":591},{"id":597,"depth":160,"text":598},{"id":604,"depth":143,"text":605},"2026-09-18","Compare Nuitka and PyInstaller for shipping a Python CLI as a standalone binary: how each works, build times, startup, size, hidden imports, CI builds and choosing.","intermediate",false,"md",{},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fnuitka-vs-pyinstaller-for-python-clis",{"title":5,"description":657},"project-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fnuitka-vs-pyinstaller-for-python-clis\u002Findex",[666,667,668,669],"nuitka","pyinstaller","binaries","distribution","Gpbesq1iok0oqId4weSR3D9I-7STbj1_aT3xqUlfF2Q",[672,675,678,681,684,687,690,693,696,699,702,705,708,711,714,717,720,723,726,729,732,735,738,741,744,747,750,753,756,759,762,765,768,771,774,777,780,783,786,789,792,795,798,801,804,807,810,813,816,819,822,825,828,831,834,837,840,843,846,849,852,855,858,861,864,867,870,873,876,879,882,885,888,891,894,897,900,903,906,909,912,915,918,921,924,927,930,933,936,939,942,945,948,951,954,957,960,963,966,969,972,975,978,981,984,987,990,993,996,999,1002,1005,1008,1011,1014,1017,1020,1023,1026,1029,1032,1035,1038,1041,1044,1047,1050,1053,1056,1059,1062,1065,1068,1071,1074,1077,1080,1083,1086,1089,1092,1095,1098,1101,1104,1107,1109,1112,1115,1116,1119,1122,1125,1128,1131,1134,1137,1140,1143,1146,1149,1152,1155,1158,1161,1164,1167,1170,1173,1176,1179,1182,1185,1188,1191,1194,1197,1200,1203,1206,1209,1212,1215],{"path":673,"title":674},"\u002Fabout","About Python CLI Toolcraft",{"path":676,"title":677},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies","Advanced Argument Validation Strategies",{"path":679,"title":680},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fparsing-nested-json-arguments-in-python-clis","Parsing Nested JSON Args in Python CLIs",{"path":682,"title":683},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-dependent-and-conflicting-options","Validating Dependent and Conflicting CLI Options",{"path":685,"title":686},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-file-and-directory-paths-in-clis","Validating File and Directory Paths in CLIs",{"path":688,"title":689},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fwriting-custom-click-parameter-types","Writing Custom Click Parameter Types",{"path":691,"title":692},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fbuilding-your-first-textual-app","Building Your First Textual App for a Python CLI",{"path":694,"title":695},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fchoosing-between-a-cli-a-prompt-flow-and-a-tui","Choosing Between a CLI, a Prompt Flow and a TUI",{"path":697,"title":698},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual","Building Terminal UIs with Textual for Python CLIs",{"path":700,"title":701},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Ftesting-textual-apps-with-pilot","Testing Textual Apps with Pilot",{"path":703,"title":704},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fadding-examples-and-epilogs-to-help-output","Adding Examples and Epilogs to Help Output",{"path":706,"title":707},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fgenerating-man-pages-and-docs-from-a-cli","Generating Man Pages and Docs from a CLI",{"path":709,"title":710},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation","CLI Help Output and Documentation",{"path":712,"title":713},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fversioning-and-deprecating-cli-flags","Versioning and Deprecating CLI Flags",{"path":715,"title":716},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fwriting-help-text-users-actually-read","Writing Help Text Users Actually Read",{"path":718,"title":719},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fadapting-output-to-terminal-width","Adapting Python CLI Output to Terminal Width",{"path":721,"title":722},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fdetecting-ci-environments-and-non-interactive-shells","Detecting CI Environments and Non-Interactive Shells",{"path":724,"title":725},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Ffixing-unicode-and-encoding-errors-on-windows","Fixing Unicode and Encoding Errors on Windows in Python CLIs",{"path":727,"title":728},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility","Cross-Platform Terminal Compatibility for Python CLIs",{"path":730,"title":731},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Frespecting-no-color-and-force-color","Respecting NO_COLOR and FORCE_COLOR in Python CLIs",{"path":733,"title":734},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fchoosing-exit-codes-for-cli-tools","Choosing Exit Codes for CLI Tools",{"path":736,"title":737},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fdesigning-an-exception-hierarchy-for-a-cli","Designing an Exception Hierarchy for a Python CLI",{"path":739,"title":740},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Ffriendly-error-messages-and-tracebacks","Friendly Error Messages and Tracebacks",{"path":742,"title":743},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fhandling-keyboard-interrupt-cleanly","Handling Keyboard Interrupt Cleanly",{"path":745,"title":746},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes","Error Handling and Exit Codes for CLIs",{"path":748,"title":749},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Freporting-machine-readable-errors-in-json-mode","Reporting Machine-Readable Errors in JSON Mode",{"path":751,"title":752},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Fconfig-precedence-flags-env-files-defaults","Config Precedence: Flags, Env, Files, Defaults",{"path":754,"title":755},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Fdiscovering-project-config-files-by-walking-up-directories","Discovering Project Config Files by Walking Up Directories",{"path":757,"title":758},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars","Handling Config Files and Env Vars in CLIs",{"path":760,"title":761},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Floading-yaml-configs-safely-in-cli-apps","Loading YAML configs safely in CLI apps",{"path":763,"title":764},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Freading-toml-config-with-tomllib","Reading TOML Config with tomllib in Python CLIs",{"path":766,"title":767},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Ftyped-settings-with-pydantic-settings","Typed Settings with pydantic-settings in Python CLIs",{"path":769,"title":770},"\u002Fadvanced-input-parsing-user-experience","Advanced Input Parsing for Python CLIs",{"path":772,"title":773},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Fadding-progress-bars-and-spinners-to-python-clis","Progress Bars and Spinners for Python CLIs",{"path":775,"title":776},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Fbuilding-interactive-prompts-and-menus","Building Interactive Prompts and Menus in Python CLIs",{"path":778,"title":779},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich","Interactive Terminal UI with Rich",{"path":781,"title":782},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Flive-dashboards-with-rich-live","Live Dashboards with Rich Live in Python CLIs",{"path":784,"title":785},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Frendering-tables-and-json-with-rich","Rendering Tables and JSON with Rich",{"path":787,"title":788},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Ftheming-rich-output-consistently","Theming Rich Output Consistently in Python CLIs",{"path":790,"title":791},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fdynamic-completion-values-from-apis-and-files","Dynamic Completion Values from APIs and Files",{"path":793,"title":794},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fenabling-tab-completion-in-click-and-typer","Enabling Tab Completion in Click and Typer",{"path":796,"title":797},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis","Shell Completion for Python CLIs",{"path":799,"title":800},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Finstalling-shell-completion-for-bash-zsh-fish","Installing Shell Completion for bash, zsh, fish",{"path":802,"title":803},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Ftesting-shell-completion-in-python-clis","Testing Shell Completion in Python CLIs",{"path":805,"title":806},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fadding-trace-ids-and-context-to-cli-logs","Adding Trace IDs and Context to Python CLI Logs",{"path":808,"title":809},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fadding-verbose-and-quiet-logging-flags","Adding Verbose and Quiet Logging Flags",{"path":811,"title":812},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps","Structured Logging for CLI Apps",{"path":814,"title":815},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fstructured-json-logging-in-python-clis","Structured JSON Logging in Python CLIs",{"path":817,"title":818},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fwriting-rotating-log-files-from-a-cli","Writing Rotating Log Files from a Python CLI",{"path":820,"title":821},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fdetecting-tty-and-adapting-output","Detecting a TTY and Adapting Output",{"path":823,"title":824},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Femitting-json-output-for-scripting","Emitting JSON Output for Scripting",{"path":826,"title":827},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fhandling-broken-pipe-and-sigpipe","Handling Broken Pipe and SIGPIPE",{"path":829,"title":830},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes","Working with stdin, stdout and Pipes",{"path":832,"title":833},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fprocessing-large-files-and-ndjson-streams","Processing Large Files and NDJSON Streams in Python CLIs",{"path":835,"title":836},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Freading-piped-input-in-python-clis","Reading Piped Input in Python CLIs",{"path":838,"title":839},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fbuilding-an-api-client-cli-with-httpx","Building an API Client CLI with httpx",{"path":841,"title":842},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fdownloading-files-with-progress-in-python","Downloading Files with Progress in Python CLIs",{"path":844,"title":845},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis","Calling HTTP APIs from Python CLIs",{"path":847,"title":848},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Foauth-device-flow-login-for-clis","OAuth Device Flow Login for Python CLIs",{"path":850,"title":851},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fpaginating-api-results-in-a-cli","Paginating API Results in a Python CLI",{"path":853,"title":854},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fretries-and-backoff-for-cli-http-calls","Retries and Backoff for CLI HTTP Calls",{"path":856,"title":857},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fcancelling-async-tasks-on-ctrl-c","Cancelling Async Tasks on Ctrl+C in Python CLIs",{"path":859,"title":860},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis","Concurrency and Async in Python CLIs",{"path":862,"title":863},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fmultiprocessing-for-cpu-bound-cli-tasks","Multiprocessing for CPU-Bound CLI Tasks",{"path":865,"title":866},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fparallelising-cli-work-with-thread-pools","Parallelising CLI Work with Thread Pools",{"path":868,"title":869},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Frate-limiting-concurrent-requests-in-clis","Rate-Limiting Concurrent Requests in Python CLIs",{"path":871,"title":872},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Frunning-async-code-in-typer-and-click","Running Async Code in Typer and Click",{"path":874,"title":875},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fcross-platform-paths-with-pathlib","Cross-Platform Paths with pathlib in CLIs",{"path":877,"title":878},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Ffile-locking-for-concurrent-cli-runs","File Locking for Concurrent CLI Runs in Python",{"path":880,"title":881},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes","Filesystem Paths and Atomic Writes for CLIs",{"path":883,"title":884},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fsafe-temporary-files-and-directories","Safe Temporary Files and Directories in CLIs",{"path":886,"title":887},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fstoring-app-data-with-platformdirs","Storing CLI App Data with platformdirs",{"path":889,"title":890},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fwriting-files-atomically-in-python-clis","Writing Files Atomically in Python CLIs",{"path":892,"title":893},"\u002Fcli-runtime-systems-integration","CLI Runtime & Systems Integration for Python",{"path":895,"title":896},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fbuilding-a-watch-mode-with-watchfiles","Building a Watch Mode with watchfiles in Python",{"path":898,"title":899},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fhandling-sigterm-and-graceful-shutdown","Handling SIGTERM and Graceful Shutdown in CLIs",{"path":901,"title":902},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fhealth-checks-and-heartbeats-for-long-running-clis","Health Checks and Heartbeats for Long-Running CLIs",{"path":904,"title":905},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis","Long-Running and Watch-Mode Python CLIs",{"path":907,"title":908},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Frunning-a-cli-on-a-schedule-with-cron-and-systemd","Running a Python CLI on a Schedule with cron and systemd",{"path":910,"title":911},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Favoiding-shell-injection-in-python-clis","Avoiding Shell Injection in Python CLIs",{"path":913,"title":914},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fcalling-external-commands-safely-with-subprocess","Calling External Commands Safely with subprocess",{"path":916,"title":917},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fhandling-subprocess-timeouts-and-exit-codes","Handling Subprocess Timeouts and Exit Codes",{"path":919,"title":920},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis","Running Subprocesses from Python CLIs",{"path":922,"title":923},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fstreaming-subprocess-output-in-real-time","Streaming Subprocess Output in Real Time",{"path":925,"title":926},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fwrapping-git-and-other-tools-from-a-python-cli","Wrapping git and Other Tools from a Python CLI",{"path":928,"title":929},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis","Secrets and Credentials in Python CLIs",{"path":931,"title":932},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fprompting-for-passwords-securely","Prompting for Passwords Securely in Python CLIs",{"path":934,"title":935},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Freading-secrets-from-env-and-files","Reading Secrets from Env Vars and Files in CLIs",{"path":937,"title":938},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fredacting-secrets-from-cli-output-and-logs","Redacting Secrets from CLI Output and Logs",{"path":940,"title":941},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fstoring-tokens-with-keyring","Storing CLI Tokens Securely with keyring",{"path":943,"title":944},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fsupporting-multiple-profiles-and-accounts","Supporting Multiple Profiles and Accounts in CLIs",{"path":946,"title":947},"\u002F","Python CLI Toolcraft",{"path":949,"title":950},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fcaching-expensive-work-between-cli-runs","Caching Expensive Work Between Python CLI Runs",{"path":952,"title":953},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading","CLI Startup Performance and Lazy Loading",{"path":955,"title":956},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Flazy-loading-subcommands-for-faster-startup","Lazy Loading Subcommands for Faster Startup",{"path":958,"title":959},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fprofiling-python-cli-startup-time","Profiling Python CLI Startup Time",{"path":961,"title":962},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Freducing-cli-dependency-weight","Reducing CLI Dependency Weight",{"path":964,"title":965},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-subparsers-for-subcommands","argparse Subparsers for Subcommands",{"path":967,"title":968},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-vs-click-vs-typer-comparison","argparse vs Click vs Typer Compared",{"path":970,"title":971},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse","Command-Line Parsing with argparse",{"path":973,"title":974},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmigrating-from-argparse-to-typer","Migrating from argparse to Typer",{"path":976,"title":977},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmutually-exclusive-options-in-argparse","Mutually Exclusive Options in argparse",{"path":979,"title":980},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fwriting-custom-argparse-actions","Writing Custom argparse Actions in Python",{"path":982,"title":983},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fadding-dry-run-and-confirmation-to-destructive-commands","Adding Dry-Run and Confirmation to Destructive Commands",{"path":985,"title":986},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Ffollowing-posix-and-gnu-argument-conventions","Following POSIX and GNU Argument Conventions in Python",{"path":988,"title":989},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fglobal-options-vs-per-command-options","Global Options vs Per-Command Options in Python CLIs",{"path":991,"title":992},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions","Designing CLI Interfaces and Conventions in Python",{"path":994,"title":995},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fnaming-commands-and-flags-consistently","Naming Commands and Flags Consistently in Python CLIs",{"path":997,"title":998},"\u002Fmodern-python-cli-frameworks-architecture","Python CLI Frameworks and Architecture",{"path":1000,"title":1001},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fdiscovering-plugins-with-entry-points","Discovering Plugins with Entry Points in Python CLIs",{"path":1003,"title":1004},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fhook-based-plugins-with-pluggy","Hook-Based Plugins for Python CLIs with pluggy",{"path":1006,"title":1007},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis","Plugin Architectures for Extensible CLIs",{"path":1009,"title":1010},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fversioning-a-plugin-api","Versioning a Plugin API for a Python CLI",{"path":1012,"title":1013},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fwriting-a-plugin-for-an-existing-cli","Writing a Plugin for an Existing CLI",{"path":1015,"title":1016},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fbest-practices-for-python-cli-entry-points","Best practices for Python CLI entry points",{"path":1018,"title":1019},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fdependency-injection-patterns-for-cli-commands","Dependency Injection Patterns for CLI Commands",{"path":1021,"title":1022},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fhow-to-structure-a-large-python-cli-project","Structuring a Large Python CLI Project",{"path":1024,"title":1025},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis","Structuring Multi-Command Python CLIs",{"path":1027,"title":1028},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-common-options-across-commands","Sharing Common Options Across Python CLI Commands",{"path":1030,"title":1031},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-state-with-click-context-objects","Sharing State with Click Context Objects",{"path":1033,"title":1034},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fend-to-end-testing-an-installed-cli","End-to-End Testing an Installed Python CLI",{"path":1036,"title":1037},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications","Testing Python CLI Applications",{"path":1039,"title":1040},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fmeasuring-cli-test-coverage","Measuring CLI Test Coverage",{"path":1042,"title":1043},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fmocking-filesystem-and-network-in-cli-tests","Mocking the Filesystem and Network in CLI Tests",{"path":1045,"title":1046},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fproperty-based-testing-cli-arguments-with-hypothesis","Property-Based Testing CLI Arguments with Hypothesis",{"path":1048,"title":1049},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fsnapshot-testing-cli-output","Snapshot Testing CLI Output",{"path":1051,"title":1052},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-click-commands-with-clirunner","Testing Click Commands with CliRunner",{"path":1054,"title":1055},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-interactive-prompts-and-stdin","Testing Interactive Prompts and stdin",{"path":1057,"title":1058},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fbuilding-a-cli-with-subcommands-in-click","Building a CLI with subcommands in Click",{"path":1060,"title":1061},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fbuilding-dynamic-commands-in-click","Building Dynamic Commands in Click",{"path":1063,"title":1064},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fconverting-a-click-app-to-typer","Converting a Click App to Typer",{"path":1066,"title":1067},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each","Typer vs Click: When to Use Each",{"path":1069,"title":1070},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Ftyper-callback-functions-explained","Typer callback functions explained",{"path":1072,"title":1073},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fusing-annotated-options-in-typer","Using Annotated Options in Typer",{"path":1075,"title":1076},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fautomating-releases-from-git-tags","Automating Python CLI Releases from Git Tags",{"path":1078,"title":1079},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fcaching-uv-dependencies-in-ci","Caching uv Dependencies in CI for Python CLIs",{"path":1081,"title":1082},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis","CI\u002FCD Pipelines for Python CLIs",{"path":1084,"title":1085},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fpublishing-to-pypi-with-trusted-publishing","Publishing a CLI to PyPI with Trusted Publishing",{"path":1087,"title":1088},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fsmoke-testing-the-built-wheel-in-ci","Smoke-Testing the Built Wheel of a Python CLI in CI",{"path":1090,"title":1091},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Ftesting-a-cli-across-python-versions-with-github-actions","Testing a CLI Across Python Versions in GitHub Actions",{"path":1093,"title":1094},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fbuilding-a-cookiecutter-template-for-typer-clis","Building a Cookiecutter Template for Typer CLIs",{"path":1096,"title":1097},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fcopier-vs-cookiecutter-for-cli-templates","Copier vs Cookiecutter for CLI Templates",{"path":1099,"title":1100},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter","CLI Project Scaffolding with Cookiecutter",{"path":1102,"title":1103},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fpost-generation-hooks-in-cli-templates","Post-Generation Hooks in Python CLI Templates",{"path":1105,"title":1106},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbuilding-cross-platform-release-binaries-in-ci","Building Cross-Platform Release Binaries in CI",{"path":1108,"title":618},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbundling-a-python-cli-with-pyinstaller",{"path":1110,"title":1111},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fhomebrew-and-scoop-packaging-for-python-clis","Homebrew and Scoop Packaging for Python CLIs",{"path":1113,"title":1114},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries","Distributing CLIs as Standalone Binaries",{"path":662,"title":5},{"path":1117,"title":1118},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fshipping-a-cli-as-a-zipapp-with-shiv","Shipping a CLI as a Zipapp with shiv",{"path":1120,"title":1121},"\u002Fproject-setup-dependency-management","Project Setup & Dependency Management",{"path":1123,"title":1124},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fconfiguring-ruff-for-a-cli-project","Configuring Ruff for a Python CLI Project",{"path":1126,"title":1127},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fenforcing-import-boundaries-in-a-cli-codebase","Enforcing Import Boundaries in a Python CLI Codebase",{"path":1129,"title":1130},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code","Linting and Type-Checking Python CLI Code",{"path":1132,"title":1133},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Ftype-checking-click-and-typer-code-with-mypy","Type-Checking Click and Typer Code with mypy",{"path":1135,"title":1136},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fautomating-changelogs-with-conventional-commits","Automating Changelogs with Conventional Commits",{"path":1138,"title":1139},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fderiving-versions-from-git-tags-with-hatch-vcs","Deriving CLI Versions from Git Tags with hatch-vcs",{"path":1141,"title":1142},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fexposing-version-info-and-build-metadata","Exposing Version Info and Build Metadata",{"path":1144,"title":1145},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs","Managing CLI Versioning & Changelogs",{"path":1147,"title":1148},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fsemantic-versioning-policy-for-cli-tools","A Semantic Versioning Policy for CLI Tools",{"path":1150,"title":1151},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbuilding-wheels-and-sdists-for-python-clis","Building Wheels and sdists for Python CLIs",{"path":1153,"title":1154},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbundling-data-files-with-importlib-resources","Bundling Data Files with importlib.resources in CLIs",{"path":1156,"title":1157},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution","Packaging Python CLIs for Distribution",{"path":1159,"title":1160},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Finstalling-and-distributing-clis-with-pipx","Installing and Distributing CLIs with pipx",{"path":1162,"title":1163},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fpublishing-a-python-cli-to-pypi","Publishing a Python CLI to PyPI",{"path":1165,"title":1166},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fwriting-pyproject-toml-metadata-for-a-cli","Writing pyproject.toml Metadata for a Python CLI",{"path":1168,"title":1169},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development","Poetry Workflows for CLI Development",{"path":1171,"title":1172},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fmigrating-a-cli-from-poetry-to-uv","Migrating a Python CLI from Poetry to uv",{"path":1174,"title":1175},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-dependency-groups-for-cli-tooling","Poetry Dependency Groups for CLI Tooling",{"path":1177,"title":1178},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-entry-points-and-scripts-for-clis","Poetry Entry Points and Scripts for CLIs",{"path":1180,"title":1181},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects","Pre-commit Hooks for CLI Projects",{"path":1183,"title":1184},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects\u002Fsetting-up-pre-commit-for-python-cli-repos","Setting up pre-commit for Python CLI repos",{"path":1186,"title":1187},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects\u002Fshipping-your-cli-as-a-pre-commit-hook","Shipping Your Python CLI as a pre-commit Hook",{"path":1189,"title":1190},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects\u002Fwriting-local-pre-commit-hooks-in-python","Writing Local pre-commit Hooks in Python",{"path":1192,"title":1193},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management","uv for Python CLI Dependency Management",{"path":1195,"title":1196},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Frunning-one-off-cli-scripts-with-uv-run","Running One-Off CLI Scripts with uv run and PEP 723",{"path":1198,"title":1199},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-init-vs-poetry-init-for-cli-tools","uv init vs poetry init for CLI tools",{"path":1201,"title":1202},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-tool-install-vs-pipx-for-clis","uv tool install vs pipx for CLIs",{"path":1204,"title":1205},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis","uv Workspaces for Multi-Package Python CLIs",{"path":1207,"title":1208},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices","Python CLI Env Isolation Best Practices",{"path":1210,"title":1211},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fmanaging-virtual-environments-for-cross-platform-clis","Managing Python CLI Virtual Environments",{"path":1213,"title":1214},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fpinning-the-python-version-for-a-cli","Pinning the Python Version for a CLI",{"path":1216,"title":1217},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fsupporting-multiple-python-versions-with-nox","Supporting Multiple Python Versions with nox",1789736907485]