[{"data":1,"prerenderedAt":2464},["ShallowReactive",2],{"page-\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002F":3,"content-directory":1619},{"id":4,"title":5,"body":6,"date":1604,"description":1605,"difficulty":1606,"draft":1607,"extension":1608,"meta":1609,"navigation":214,"path":1610,"seo":1611,"stem":1612,"tags":1613,"updated":1604,"__hash__":1618},"content\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Findex.md","Beyond Click and Typer: Alternative Python CLI Frameworks",{"type":7,"value":8,"toc":1583},"minimark",[9,35,54,58,63,98,102,105,108,138,149,152,156,163,168,464,470,554,559,638,643,894,897,901,904,939,957,967,990,1015,1019,1022,1025,1079,1083,1095,1206,1214,1218,1221,1224,1286,1294,1298,1301,1341,1349,1353,1356,1411,1414,1418,1456,1460,1481,1485,1490,1504,1508,1518,1522,1525,1529,1532,1536,1539,1543,1579],[10,11,12,13,17,18,21,22,25,26,30,31,34],"p",{},"argparse, Click and Typer cover the large majority of Python command-line tools, and most of this site uses them. But they are not the only serious options, and the alternatives are not just historical curiosities. ",[14,15,16],"strong",{},"Cyclopts"," takes Typer's type-hint idea and fixes several of its rough edges. ",[14,19,20],{},"Python Fire"," turns any object into a CLI with one line, which is unbeatable for internal scripts. ",[14,23,24],{},"docopt-ng"," keeps the idea that the help text ",[27,28,29],"em",{},"is"," the parser. ",[14,32,33],{},"Cleo"," is the command-class framework behind Poetry, with a console layer built for long-lived, many-command applications. Each makes a different trade, and knowing those trades helps you choose deliberately — or recognise the framework in a codebase you have just inherited.",[10,36,37,38,43,44,48,49,53],{},"This topic surveys the four, shows each one doing the same job, and compares them on the things that matter in production: how arguments are declared, how types are converted, what happens on bad input, how you test, and what exit codes you get. It sits in the ",[39,40,42],"a",{"href":41},"\u002Fmodern-python-cli-frameworks-architecture\u002F","Modern Python CLI Frameworks & Architecture"," section, next to ",[39,45,47],{"href":46},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002F","command-line parsing with argparse"," and ",[39,50,52],{"href":51},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002F","Typer vs Click: when to use each",", which remain the reference points.",[55,56],"inline-diagram",{"name":57},"altfw-topic-map",[59,60,62],"h2",{"id":61},"tldr","TL;DR",[64,65,66,77,82,87,92],"ul",{},[67,68,69,71,72,76],"li",{},[14,70,16],{}," — type hints and docstrings define the interface, like Typer, but with first-class ",[73,74,75],"code",{},"Literal",", unions, dataclasses, config sources and docstring-parsed help. A strong choice for new type-hinted CLIs.",[67,78,79,81],{},[14,80,20],{}," — exposes functions, classes or modules with no declarations at all. Ideal for a team's internal scripts and exploration; too loose for a public tool, because it does not enforce types.",[67,83,84,86],{},[14,85,24],{}," — the usage text you write is parsed into a grammar. Elegant for small tools with a stable interface; every value arrives as a string, and validation is yours.",[67,88,89,91],{},[14,90,33],{}," — commands are classes with declared arguments and options, plus rich console I\u002FO, verbosity levels and testers. Good for large applications that want structure over decorators; it powers Poetry.",[67,93,94,97],{},[14,95,96],{},"Click and Typer remain the default"," for most projects because of their ecosystem: plugins, completion, testing helpers and documentation. Pick an alternative for a concrete reason.",[59,99,101],{"id":100},"four-ways-to-declare-an-interface","Four ways to declare an interface",[10,103,104],{},"Every CLI framework answers one question: where does the description of the command line live? The answer shapes everything downstream — how much code you write, where the help comes from, and how much the parser knows about types.",[55,106],{"name":107},"altfw-declaration-models",[109,110,111,117,126,132],"ol",{},[67,112,113,116],{},[14,114,115],{},"Decorators or builder calls"," (Click, argparse). You describe each parameter explicitly, next to the function or on a parser object. Verbose, unambiguous, and very flexible.",[67,118,119,122,123,125],{},[14,120,121],{},"Type-annotated signatures"," (Typer, Cyclopts). The function signature ",[27,124,29],{}," the declaration; annotations drive conversion and validation, and docstrings or annotations supply help.",[67,127,128,131],{},[14,129,130],{},"Usage text"," (docopt). You write the help message in a conventional format and the library derives a parser from it.",[67,133,134,137],{},[14,135,136],{},"Introspection with no declaration"," (Fire). The library inspects whatever object you hand it and exposes its callables and parameters as commands and flags.",[10,139,140,141,144,145,148],{},"A fifth model, ",[14,142,143],{},"command classes"," (Cleo, and Cement or Cliff in the wider ecosystem), sits between the first two: each command is a class with declared arguments and a ",[73,146,147],{},"handle()"," method, which suits applications with dozens of commands sharing services.",[10,150,151],{},"The further you move from explicit declaration, the less code you write and the less the framework can check for you. Fire knows nothing about the type of a parameter unless the value happens to parse as a Python literal; Click knows exactly what you told it. That single axis explains most of the differences in the rest of this topic.",[59,153,155],{"id":154},"the-same-command-in-each-framework","The same command in each framework",[10,157,158,159,162],{},"A small command makes the comparison concrete: ",[73,160,161],{},"add TEXT [--tag TAG]... [--priority 1-5]",".",[10,164,165,167],{},[14,166,16],{}," reads the signature and the NumPy- or Google-style docstring:",[169,170,175],"pre",{"className":171,"code":172,"language":173,"meta":174,"style":174},"language-python shiki shiki-themes github-light github-dark","from typing import Annotated\nfrom cyclopts import App, Parameter, validators\n\napp = App(name=\"notes\", version=\"1.2.0\")\n\n\n@app.command\ndef add(\n    text: str,\n    *,\n    tag: Annotated[list[str] | None, Parameter(name=[\"--tag\", \"-t\"])] = None,\n    priority: Annotated[int, Parameter(validator=validators.Number(gte=1, lte=5))] = 3,\n):\n    \"\"\"Add a note.\n\n    Parameters\n    ----------\n    text\n        The note text.\n    tag\n        Tags to attach; repeat the flag.\n    priority\n        1 (low) to 5 (high).\n    \"\"\"\n","python","",[73,176,177,196,209,216,252,257,262,269,281,294,302,346,393,399,405,410,416,422,428,434,440,446,452,458],{"__ignoreMap":174},[178,179,182,186,190,193],"span",{"class":180,"line":181},"line",1,[178,183,185],{"class":184},"szBVR","from",[178,187,189],{"class":188},"sVt8B"," typing ",[178,191,192],{"class":184},"import",[178,194,195],{"class":188}," Annotated\n",[178,197,199,201,204,206],{"class":180,"line":198},2,[178,200,185],{"class":184},[178,202,203],{"class":188}," cyclopts ",[178,205,192],{"class":184},[178,207,208],{"class":188}," App, Parameter, validators\n",[178,210,212],{"class":180,"line":211},3,[178,213,215],{"emptyLinePlaceholder":214},true,"\n",[178,217,219,222,225,228,232,234,238,241,244,246,249],{"class":180,"line":218},4,[178,220,221],{"class":188},"app ",[178,223,224],{"class":184},"=",[178,226,227],{"class":188}," App(",[178,229,231],{"class":230},"s4XuR","name",[178,233,224],{"class":184},[178,235,237],{"class":236},"sZZnC","\"notes\"",[178,239,240],{"class":188},", ",[178,242,243],{"class":230},"version",[178,245,224],{"class":184},[178,247,248],{"class":236},"\"1.2.0\"",[178,250,251],{"class":188},")\n",[178,253,255],{"class":180,"line":254},5,[178,256,215],{"emptyLinePlaceholder":214},[178,258,260],{"class":180,"line":259},6,[178,261,215],{"emptyLinePlaceholder":214},[178,263,265],{"class":180,"line":264},7,[178,266,268],{"class":267},"sScJk","@app.command\n",[178,270,272,275,278],{"class":180,"line":271},8,[178,273,274],{"class":184},"def",[178,276,277],{"class":267}," add",[178,279,280],{"class":188},"(\n",[178,282,284,287,291],{"class":180,"line":283},9,[178,285,286],{"class":188},"    text: ",[178,288,290],{"class":289},"sj4cs","str",[178,292,293],{"class":188},",\n",[178,295,297,300],{"class":180,"line":296},10,[178,298,299],{"class":184},"    *",[178,301,293],{"class":188},[178,303,305,308,310,313,316,319,322,324,326,329,332,334,337,340,342,344],{"class":180,"line":304},11,[178,306,307],{"class":188},"    tag: Annotated[list[",[178,309,290],{"class":289},[178,311,312],{"class":188},"] ",[178,314,315],{"class":184},"|",[178,317,318],{"class":289}," None",[178,320,321],{"class":188},", Parameter(",[178,323,231],{"class":230},[178,325,224],{"class":184},[178,327,328],{"class":188},"[",[178,330,331],{"class":236},"\"--tag\"",[178,333,240],{"class":188},[178,335,336],{"class":236},"\"-t\"",[178,338,339],{"class":188},"])] ",[178,341,224],{"class":184},[178,343,318],{"class":289},[178,345,293],{"class":188},[178,347,349,352,355,357,360,362,365,368,370,373,375,378,380,383,386,388,391],{"class":180,"line":348},12,[178,350,351],{"class":188},"    priority: Annotated[",[178,353,354],{"class":289},"int",[178,356,321],{"class":188},[178,358,359],{"class":230},"validator",[178,361,224],{"class":184},[178,363,364],{"class":188},"validators.Number(",[178,366,367],{"class":230},"gte",[178,369,224],{"class":184},[178,371,372],{"class":289},"1",[178,374,240],{"class":188},[178,376,377],{"class":230},"lte",[178,379,224],{"class":184},[178,381,382],{"class":289},"5",[178,384,385],{"class":188},"))] ",[178,387,224],{"class":184},[178,389,390],{"class":289}," 3",[178,392,293],{"class":188},[178,394,396],{"class":180,"line":395},13,[178,397,398],{"class":188},"):\n",[178,400,402],{"class":180,"line":401},14,[178,403,404],{"class":236},"    \"\"\"Add a note.\n",[178,406,408],{"class":180,"line":407},15,[178,409,215],{"emptyLinePlaceholder":214},[178,411,413],{"class":180,"line":412},16,[178,414,415],{"class":236},"    Parameters\n",[178,417,419],{"class":180,"line":418},17,[178,420,421],{"class":236},"    ----------\n",[178,423,425],{"class":180,"line":424},18,[178,426,427],{"class":236},"    text\n",[178,429,431],{"class":180,"line":430},19,[178,432,433],{"class":236},"        The note text.\n",[178,435,437],{"class":180,"line":436},20,[178,438,439],{"class":236},"    tag\n",[178,441,443],{"class":180,"line":442},21,[178,444,445],{"class":236},"        Tags to attach; repeat the flag.\n",[178,447,449],{"class":180,"line":448},22,[178,450,451],{"class":236},"    priority\n",[178,453,455],{"class":180,"line":454},23,[178,456,457],{"class":236},"        1 (low) to 5 (high).\n",[178,459,461],{"class":180,"line":460},24,[178,462,463],{"class":236},"    \"\"\"\n",[10,465,466,469],{},[14,467,468],{},"Fire"," needs nothing but the function — and enforces nothing either:",[169,471,473],{"className":171,"code":472,"language":173,"meta":174,"style":174},"import fire\n\ndef add(text: str, tag: tuple = (), priority: int = 3):\n    \"\"\"Add a note.\"\"\"\n\nif __name__ == \"__main__\":\n    fire.Fire({\"add\": add})\n",[73,474,475,482,486,517,522,526,543],{"__ignoreMap":174},[178,476,477,479],{"class":180,"line":181},[178,478,192],{"class":184},[178,480,481],{"class":188}," fire\n",[178,483,484],{"class":180,"line":198},[178,485,215],{"emptyLinePlaceholder":214},[178,487,488,490,492,495,497,500,503,506,509,511,513,515],{"class":180,"line":211},[178,489,274],{"class":184},[178,491,277],{"class":267},[178,493,494],{"class":188},"(text: ",[178,496,290],{"class":289},[178,498,499],{"class":188},", tag: ",[178,501,502],{"class":289},"tuple",[178,504,505],{"class":184}," =",[178,507,508],{"class":188}," (), priority: ",[178,510,354],{"class":289},[178,512,505],{"class":184},[178,514,390],{"class":289},[178,516,398],{"class":188},[178,518,519],{"class":180,"line":218},[178,520,521],{"class":236},"    \"\"\"Add a note.\"\"\"\n",[178,523,524],{"class":180,"line":254},[178,525,215],{"emptyLinePlaceholder":214},[178,527,528,531,534,537,540],{"class":180,"line":259},[178,529,530],{"class":184},"if",[178,532,533],{"class":289}," __name__",[178,535,536],{"class":184}," ==",[178,538,539],{"class":236}," \"__main__\"",[178,541,542],{"class":188},":\n",[178,544,545,548,551],{"class":180,"line":264},[178,546,547],{"class":188},"    fire.Fire({",[178,549,550],{"class":236},"\"add\"",[178,552,553],{"class":188},": add})\n",[10,555,556,558],{},[14,557,24],{}," parses a usage string:",[169,560,562],{"className":171,"code":561,"language":173,"meta":174,"style":174},"\"\"\"Notes.\n\nUsage:\n  notes add \u003Ctext> [--tag=\u003Ctag>]... [--priority=\u003Cn>]\n\nOptions:\n  --priority=\u003Cn>  1 (low) to 5 (high) [default: 3].\n\"\"\"\nfrom docopt import docopt\n\nargs = docopt(__doc__)          # {'\u003Ctext>': ..., '--tag': [...], '--priority': '3', ...}\n",[73,563,564,569,573,578,583,587,592,597,602,614,618],{"__ignoreMap":174},[178,565,566],{"class":180,"line":181},[178,567,568],{"class":236},"\"\"\"Notes.\n",[178,570,571],{"class":180,"line":198},[178,572,215],{"emptyLinePlaceholder":214},[178,574,575],{"class":180,"line":211},[178,576,577],{"class":236},"Usage:\n",[178,579,580],{"class":180,"line":218},[178,581,582],{"class":236},"  notes add \u003Ctext> [--tag=\u003Ctag>]... [--priority=\u003Cn>]\n",[178,584,585],{"class":180,"line":254},[178,586,215],{"emptyLinePlaceholder":214},[178,588,589],{"class":180,"line":259},[178,590,591],{"class":236},"Options:\n",[178,593,594],{"class":180,"line":264},[178,595,596],{"class":236},"  --priority=\u003Cn>  1 (low) to 5 (high) [default: 3].\n",[178,598,599],{"class":180,"line":271},[178,600,601],{"class":236},"\"\"\"\n",[178,603,604,606,609,611],{"class":180,"line":283},[178,605,185],{"class":184},[178,607,608],{"class":188}," docopt ",[178,610,192],{"class":184},[178,612,613],{"class":188}," docopt\n",[178,615,616],{"class":180,"line":296},[178,617,215],{"emptyLinePlaceholder":214},[178,619,620,623,625,628,631,634],{"class":180,"line":304},[178,621,622],{"class":188},"args ",[178,624,224],{"class":184},[178,626,627],{"class":188}," docopt(",[178,629,630],{"class":289},"__doc__",[178,632,633],{"class":188},")          ",[178,635,637],{"class":636},"sJ8bj","# {'\u003Ctext>': ..., '--tag': [...], '--priority': '3', ...}\n",[10,639,640,642],{},[14,641,33],{}," declares a command class:",[169,644,646],{"className":171,"code":645,"language":173,"meta":174,"style":174},"from cleo.commands.command import Command\nfrom cleo.helpers import argument, option\n\nclass AddCommand(Command):\n    name = \"add\"\n    description = \"Add a note.\"\n    arguments = [argument(\"text\", description=\"The note text.\")]\n    options = [\n        option(\"tag\", \"t\", description=\"Tags to attach.\", flag=False, multiple=True),\n        option(\"priority\", None, description=\"1 (low) to 5 (high).\", flag=False, default=\"3\"),\n    ]\n\n    def handle(self) -> int:\n        priority = int(self.option(\"priority\"))\n        ...\n        return 0\n",[73,647,648,660,672,676,692,702,712,738,748,793,834,839,843,858,881,886],{"__ignoreMap":174},[178,649,650,652,655,657],{"class":180,"line":181},[178,651,185],{"class":184},[178,653,654],{"class":188}," cleo.commands.command ",[178,656,192],{"class":184},[178,658,659],{"class":188}," Command\n",[178,661,662,664,667,669],{"class":180,"line":198},[178,663,185],{"class":184},[178,665,666],{"class":188}," cleo.helpers ",[178,668,192],{"class":184},[178,670,671],{"class":188}," argument, option\n",[178,673,674],{"class":180,"line":211},[178,675,215],{"emptyLinePlaceholder":214},[178,677,678,681,684,687,690],{"class":180,"line":218},[178,679,680],{"class":184},"class",[178,682,683],{"class":267}," AddCommand",[178,685,686],{"class":188},"(",[178,688,689],{"class":267},"Command",[178,691,398],{"class":188},[178,693,694,697,699],{"class":180,"line":254},[178,695,696],{"class":188},"    name ",[178,698,224],{"class":184},[178,700,701],{"class":236}," \"add\"\n",[178,703,704,707,709],{"class":180,"line":259},[178,705,706],{"class":188},"    description ",[178,708,224],{"class":184},[178,710,711],{"class":236}," \"Add a note.\"\n",[178,713,714,717,719,722,725,727,730,732,735],{"class":180,"line":264},[178,715,716],{"class":188},"    arguments ",[178,718,224],{"class":184},[178,720,721],{"class":188}," [argument(",[178,723,724],{"class":236},"\"text\"",[178,726,240],{"class":188},[178,728,729],{"class":230},"description",[178,731,224],{"class":184},[178,733,734],{"class":236},"\"The note text.\"",[178,736,737],{"class":188},")]\n",[178,739,740,743,745],{"class":180,"line":271},[178,741,742],{"class":188},"    options ",[178,744,224],{"class":184},[178,746,747],{"class":188}," [\n",[178,749,750,753,756,758,761,763,765,767,770,772,775,777,780,782,785,787,790],{"class":180,"line":283},[178,751,752],{"class":188},"        option(",[178,754,755],{"class":236},"\"tag\"",[178,757,240],{"class":188},[178,759,760],{"class":236},"\"t\"",[178,762,240],{"class":188},[178,764,729],{"class":230},[178,766,224],{"class":184},[178,768,769],{"class":236},"\"Tags to attach.\"",[178,771,240],{"class":188},[178,773,774],{"class":230},"flag",[178,776,224],{"class":184},[178,778,779],{"class":289},"False",[178,781,240],{"class":188},[178,783,784],{"class":230},"multiple",[178,786,224],{"class":184},[178,788,789],{"class":289},"True",[178,791,792],{"class":188},"),\n",[178,794,795,797,800,802,805,807,809,811,814,816,818,820,822,824,827,829,832],{"class":180,"line":296},[178,796,752],{"class":188},[178,798,799],{"class":236},"\"priority\"",[178,801,240],{"class":188},[178,803,804],{"class":289},"None",[178,806,240],{"class":188},[178,808,729],{"class":230},[178,810,224],{"class":184},[178,812,813],{"class":236},"\"1 (low) to 5 (high).\"",[178,815,240],{"class":188},[178,817,774],{"class":230},[178,819,224],{"class":184},[178,821,779],{"class":289},[178,823,240],{"class":188},[178,825,826],{"class":230},"default",[178,828,224],{"class":184},[178,830,831],{"class":236},"\"3\"",[178,833,792],{"class":188},[178,835,836],{"class":180,"line":304},[178,837,838],{"class":188},"    ]\n",[178,840,841],{"class":180,"line":348},[178,842,215],{"emptyLinePlaceholder":214},[178,844,845,848,851,854,856],{"class":180,"line":395},[178,846,847],{"class":184},"    def",[178,849,850],{"class":267}," handle",[178,852,853],{"class":188},"(self) -> ",[178,855,354],{"class":289},[178,857,542],{"class":188},[178,859,860,863,865,868,870,873,876,878],{"class":180,"line":401},[178,861,862],{"class":188},"        priority ",[178,864,224],{"class":184},[178,866,867],{"class":289}," int",[178,869,686],{"class":188},[178,871,872],{"class":289},"self",[178,874,875],{"class":188},".option(",[178,877,799],{"class":236},[178,879,880],{"class":188},"))\n",[178,882,883],{"class":180,"line":407},[178,884,885],{"class":289},"        ...\n",[178,887,888,891],{"class":180,"line":412},[178,889,890],{"class":184},"        return",[178,892,893],{"class":289}," 0\n",[10,895,896],{},"Notice where validation lives. Cyclopts enforces the 1–5 range before your function runs. Fire, docopt and Cleo hand you a value — a Python literal, a string, a string — and the range check is your code. That is the practical cost of the lighter declaration models.",[59,898,900],{"id":899},"how-they-compare-in-production","How they compare in production",[55,902],{"name":903},"altfw-comparison",[10,905,906,909,910,912,913,916,917,920,921,924,925,928,929,240,932,935,936,938],{},[14,907,908],{},"Type conversion."," Typer and Cyclopts convert from annotations; Cyclopts additionally handles ",[73,911,75],{},", unions, ",[73,914,915],{},"dataclass"," and Pydantic models as parameter groups without plugins. Click converts from declared ",[73,918,919],{},"type="," objects. Fire evaluates each value as a Python literal if it can, so ",[73,922,923],{},"07"," stays the ",[27,926,927],{},"string"," ",[73,930,931],{},"\"07\"",[73,933,934],{},"640,"," becomes a tuple and ",[73,937,789],{}," a boolean — surprising for users who never wrote Python. docopt returns strings, booleans for flags and lists for repeated items. Cleo returns strings.",[10,940,941,944,945,948,949,951,952,956],{},[14,942,943],{},"Bad input and exit codes."," Click, Typer, Cyclopts and Fire exit with code ",[73,946,947],{},"2"," on a usage error, matching the convention scripts expect. docopt-ng and Cleo exit with ",[73,950,372],{},", which a wrapper script cannot distinguish from a runtime failure. If exit codes matter to your users — see ",[39,953,955],{"href":954},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fchoosing-exit-codes-for-cli-tools\u002F","choosing exit codes for CLI tools"," — wrap the entry point or check for it in tests.",[10,958,959,962,963,966],{},[14,960,961],{},"Help output."," Cyclopts renders Rich-formatted help panels from docstrings; Fire generates man-page-style help from introspection; docopt's help is exactly the text you wrote; Cleo prints a Symfony-style command list with namespaces (",[73,964,965],{},"db migrate",") and \"did you mean\" suggestions.",[10,968,969,972,973,976,977,980,981,984,985,989],{},[14,970,971],{},"Shell completion."," Click and Typer ship completion for bash, zsh and fish. Cyclopts can generate and install completion scripts. Fire prints a bash completion script with ",[73,974,975],{},"mytool -- --completion",". docopt has no built-in completion. Cleo ships a ",[73,978,979],{},"CompletionsCommand"," you register on the application (Poetry exposes it as ",[73,982,983],{},"poetry completions","). If completion is a must-have, test it early with ",[39,986,988],{"href":987},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Ftesting-shell-completion-in-python-clis\u002F","testing shell completion"," in mind.",[10,991,992,995,996,999,1000,1003,1004,1007,1008,48,1011,1014],{},[14,993,994],{},"Testing."," Click and Typer have ",[73,997,998],{},"CliRunner",". Cyclopts apps are callable with a token list and can return the command's value directly. Fire accepts ",[73,1001,1002],{},"command=[...]"," and returns the result. docopt accepts ",[73,1005,1006],{},"argv=[...]",". Cleo has ",[73,1009,1010],{},"CommandTester",[73,1012,1013],{},"ApplicationTester"," with captured input and output.",[59,1016,1018],{"id":1017},"choosing-one","Choosing one",[55,1020],{"name":1021},"altfw-choose",[10,1023,1024],{},"Start from the default and look for a concrete reason to move.",[64,1026,1027,1041,1051,1062,1073],{},[67,1028,1029,1032,1033,1035,1036,1040],{},[14,1030,1031],{},"New public tool, type-hinted codebase:"," Typer or Cyclopts. Choose Cyclopts if you hit Typer's limits with unions, ",[73,1034,75],{},", dataclass parameters or config-file integration, or prefer docstring-driven help; choose Typer for its larger ecosystem and Click compatibility. ",[39,1037,1039],{"href":1038},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cyclopts\u002F","Building a CLI with Cyclopts"," walks through a full example.",[67,1042,1043,1046,1047,162],{},[14,1044,1045],{},"Internal script you want callable from the shell today:"," Fire. It turns a module of functions into a CLI in one line; accept that it is loose and do not ship it to customers. See ",[39,1048,1050],{"href":1049},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fquick-clis-from-functions-with-python-fire\u002F","quick CLIs from functions with Python Fire",[67,1052,1053,1056,1057,1061],{},[14,1054,1055],{},"Small tool where the usage text is the spec:"," docopt-ng, as long as you are happy validating strings yourself. ",[39,1058,1060],{"href":1059},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fusage-string-driven-clis-with-docopt-ng\u002F","Usage-string driven CLIs with docopt-ng"," shows how to pair it with a validation layer.",[67,1063,1064,1067,1068,1072],{},[14,1065,1066],{},"Large application with many commands, namespaces and shared services:"," Cleo, or Click with a class-based structure. ",[39,1069,1071],{"href":1070},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cleo\u002F","Building a CLI with Cleo"," covers commands, I\u002FO and testers.",[67,1074,1075,1078],{},[14,1076,1077],{},"Zero dependencies:"," argparse, still. Every alternative here is a third-party package.",[59,1080,1082],{"id":1081},"keeping-the-framework-replaceable","Keeping the framework replaceable",[10,1084,1085,1086,1090,1091,1094],{},"Whichever you pick, the advice from ",[39,1087,1089],{"href":1088},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fhow-to-structure-a-large-python-cli-project\u002F","how to structure a large Python CLI project"," applies doubly with less common frameworks: keep the framework in a thin outer layer. Commands parse and validate input, then call plain functions that know nothing about Cyclopts, Fire or Cleo. Business logic tested without the CLI survives a framework change; logic tangled with ",[73,1092,1093],{},"self.option()"," calls does not.",[169,1096,1098],{"className":171,"code":1097,"language":173,"meta":174,"style":174},"# core.py — no framework imports\ndef add_note(store, text: str, tags: list[str], priority: int) -> int:\n    if not 1 \u003C= priority \u003C= 5:\n        raise ValueError(\"priority must be between 1 and 5\")\n    return store.insert(text=text, tags=tags, priority=priority)\n",[73,1099,1100,1105,1134,1159,1174],{"__ignoreMap":174},[178,1101,1102],{"class":180,"line":181},[178,1103,1104],{"class":636},"# core.py — no framework imports\n",[178,1106,1107,1109,1112,1115,1117,1120,1122,1125,1127,1130,1132],{"class":180,"line":198},[178,1108,274],{"class":184},[178,1110,1111],{"class":267}," add_note",[178,1113,1114],{"class":188},"(store, text: ",[178,1116,290],{"class":289},[178,1118,1119],{"class":188},", tags: list[",[178,1121,290],{"class":289},[178,1123,1124],{"class":188},"], priority: ",[178,1126,354],{"class":289},[178,1128,1129],{"class":188},") -> ",[178,1131,354],{"class":289},[178,1133,542],{"class":188},[178,1135,1136,1139,1142,1145,1148,1151,1154,1157],{"class":180,"line":211},[178,1137,1138],{"class":184},"    if",[178,1140,1141],{"class":184}," not",[178,1143,1144],{"class":289}," 1",[178,1146,1147],{"class":184}," \u003C=",[178,1149,1150],{"class":188}," priority ",[178,1152,1153],{"class":184},"\u003C=",[178,1155,1156],{"class":289}," 5",[178,1158,542],{"class":188},[178,1160,1161,1164,1167,1169,1172],{"class":180,"line":218},[178,1162,1163],{"class":184},"        raise",[178,1165,1166],{"class":289}," ValueError",[178,1168,686],{"class":188},[178,1170,1171],{"class":236},"\"priority must be between 1 and 5\"",[178,1173,251],{"class":188},[178,1175,1176,1179,1182,1185,1187,1190,1193,1195,1198,1201,1203],{"class":180,"line":254},[178,1177,1178],{"class":184},"    return",[178,1180,1181],{"class":188}," store.insert(",[178,1183,1184],{"class":230},"text",[178,1186,224],{"class":184},[178,1188,1189],{"class":188},"text, ",[178,1191,1192],{"class":230},"tags",[178,1194,224],{"class":184},[178,1196,1197],{"class":188},"tags, ",[178,1199,1200],{"class":230},"priority",[178,1202,224],{"class":184},[178,1204,1205],{"class":188},"priority)\n",[10,1207,1208,1209,1213],{},"With that split, switching frameworks — or supporting two entry points during a migration, as in ",[39,1210,1212],{"href":1211},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmigrating-from-argparse-to-typer\u002F","migrating from argparse to Typer"," — is a matter of rewriting the outer layer.",[59,1215,1217],{"id":1216},"testing-looks-different-in-each-framework","Testing looks different in each framework",[10,1219,1220],{},"The shape of a framework's test support says a lot about how it expects to be used, and it is worth checking before you commit, because tests are where you spend time every week.",[55,1222],{"name":1223},"altfw-testing",[64,1225,1226,1239,1251,1259,1275],{},[67,1227,1228,1231,1232,1234,1235,162],{},[14,1229,1230],{},"Click and Typer"," offer ",[73,1233,998],{},", which invokes a command in-process, captures stdout and stderr, and returns an exit code and exception. Tests assert on text and codes; see ",[39,1236,1238],{"href":1237},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-click-commands-with-clirunner\u002F","testing Click commands with CliRunner",[67,1240,1241,1243,1244,1247,1248,162],{},[14,1242,16],{}," apps are callable: ",[73,1245,1246],{},"app([\"add\", \"x\"], result_action=\"return_value\")"," returns whatever the command returned, so many tests can assert on Python values rather than parsing output. Parse errors surface as exceptions when ",[73,1249,1250],{},"exit_on_error=False",[67,1252,1253,1255,1256,1258],{},[14,1254,468],{}," accepts ",[73,1257,1002],{}," and returns the result too. Because Fire does not validate types, the most valuable tests are the ones that pin what a function receives for awkward input.",[67,1260,1261,1263,1264,1267,1268,1271,1272,162],{},[14,1262,24],{}," is pure parsing: ",[73,1265,1266],{},"docopt(doc, argv=[...])"," returns the dictionary. Everything after that is your code, tested like any other function — which is why the docopt guide structures the program as ",[73,1269,1270],{},"parse()",", a conversion layer and ",[73,1273,1274],{},"main(argv)",[67,1276,1277,1279,1280,1282,1283,1285],{},[14,1278,33],{}," provides ",[73,1281,1010],{}," for a single command and ",[73,1284,1013],{}," for the whole application, both with simulated input for questions and separate captured streams.",[10,1287,1288,1289,1293],{},"Whatever the framework, the advice from ",[39,1290,1292],{"href":1291},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002F","the testing topic"," holds: test business logic without the CLI, test the CLI layer for parsing, exit codes and stream separation, and keep at least one end-to-end test that runs the installed command.",[59,1295,1297],{"id":1296},"startup-time-and-dependency-weight","Startup time and dependency weight",[10,1299,1300],{},"Framework choice also affects how fast the tool starts, which users feel on every invocation and especially in shell completion. The differences are mostly about what each framework imports at startup:",[64,1302,1303,1308,1317,1327,1336],{},[67,1304,1305,1307],{},[14,1306,24],{}," is a single small module with no dependencies, so it adds almost nothing.",[67,1309,1310,1312,1313,1316],{},[14,1311,468],{}," imports its own modules plus ",[73,1314,1315],{},"termcolor","; it is light, but it introspects the component on every run.",[67,1318,1319,1322,1323,1326],{},[14,1320,1321],{},"Click"," is moderate; ",[14,1324,1325],{},"Typer"," adds Rich for help and error formatting, which is the largest share of its import time unless help is rendered.",[67,1328,1329,1331,1332,1335],{},[14,1330,16],{}," also depends on Rich and on ",[73,1333,1334],{},"attrs",", and imports them lazily where it can.",[67,1337,1338,1340],{},[14,1339,33],{}," is moderate and supports lazy command loading for large applications.",[10,1342,1343,1344,1348],{},"For most tools the framework is not the bottleneck — your own imports are. Measure rather than guess, with the techniques in ",[39,1345,1347],{"href":1346},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fprofiling-python-cli-startup-time\u002F","profiling Python CLI startup time",", before choosing a framework for speed.",[59,1350,1352],{"id":1351},"evaluating-a-framework-you-have-not-used","Evaluating a framework you have not used",[10,1354,1355],{},"New CLI frameworks appear every year, and most are pleasant in a ten-line demo. A short, repeatable evaluation separates the ones that hold up. Build the same small tool in each candidate — one command with a required argument, a repeatable option, a choice option, a boolean flag and a subcommand group — and check these points in order:",[109,1357,1358,1364,1374,1390,1399,1405],{},[67,1359,1360,1363],{},[14,1361,1362],{},"Bad input."," Pass a wrong type, an unknown option and a missing argument. Is the message clear, does it go to stderr, and is the exit code 2?",[67,1365,1366,1369,1370,1373],{},[14,1367,1368],{},"Help."," Does ",[73,1371,1372],{},"--help"," show defaults, choices and descriptions without duplication in your code? Does it look reasonable at 80 columns and in a pipe?",[67,1375,1376,1379,1380,240,1383,1386,1387,1389],{},[14,1377,1378],{},"Types."," Do ",[73,1381,1382],{},"Path",[73,1384,1385],{},"Enum"," or ",[73,1388,75],{},", optional values and lists behave as the annotations or declarations say?",[67,1391,1392,1394,1395,1398],{},[14,1393,994],{}," Can you invoke a command in-process, capture both streams and inspect the exit code, without monkeypatching ",[73,1396,1397],{},"sys.argv","?",[67,1400,1401,1404],{},[14,1402,1403],{},"Completion."," Can users install completion for their shell, and can you test it?",[67,1406,1407,1410],{},[14,1408,1409],{},"Maintenance."," When was the last release, how many people contribute, and does it support the newest Python version?",[10,1412,1413],{},"Half an hour of this tells you more than any feature list, and the throwaway tool doubles as a reference when you write the real one.",[59,1415,1417],{"id":1416},"common-pitfalls","Common pitfalls",[64,1419,1420,1426,1435,1444,1450],{},[67,1421,1422,1425],{},[14,1423,1424],{},"Shipping Fire to end users."," Its literal parsing, permissive flags and Python-flavoured help confuse people who are not Python developers, and every public method becomes a command. Wrap the functions you want in an explicit dictionary at least.",[67,1427,1428,928,1431,1434],{},[14,1429,1430],{},"Trusting docopt values.",[73,1432,1433],{},"--priority=abc"," parses fine and fails three functions later. Validate the dictionary immediately after parsing.",[67,1436,1437,1440,1441,1443],{},[14,1438,1439],{},"Ignoring exit codes."," docopt-ng and Cleo return ",[73,1442,372],{}," for usage errors. Decide whether that matters and test for whatever you choose.",[67,1445,1446,1449],{},[14,1447,1448],{},"Mixing frameworks."," Adding a Click group to a Cleo app, or a Typer sub-app to a Cyclopts app, doubles the dependency weight and splits the help output. Choose one per executable.",[67,1451,1452,1455],{},[14,1453,1454],{},"Picking on novelty."," An unfamiliar framework costs every future contributor some learning. The benefit should be concrete: less code, a feature you need, or a better fit for the codebase.",[59,1457,1459],{"id":1458},"key-takeaways","Key takeaways",[64,1461,1462,1469,1472,1475,1478],{},[67,1463,1464,1465,1468],{},"Frameworks differ mainly in ",[27,1466,1467],{},"where the interface is declared",": decorators, type hints, usage text, introspection or command classes.",[67,1470,1471],{},"Less declaration means less code and less validation; budget for doing that validation yourself.",[67,1473,1474],{},"Cyclopts is the strongest alternative for type-hinted public tools; Fire is excellent for internal scripts; docopt suits small, stable tools; Cleo suits large, namespaced applications.",[67,1476,1477],{},"Check exit codes, completion and testing support before committing — they differ more than the parsing does.",[67,1479,1480],{},"Keep business logic framework-free so the choice stays reversible.",[59,1482,1484],{"id":1483},"frequently-asked-questions","Frequently asked questions",[1486,1487,1489],"h3",{"id":1488},"is-docopt-still-maintained","Is docopt still maintained?",[10,1491,1492,1493,1496,1497,1499,1500,1503],{},"The original ",[73,1494,1495],{},"docopt"," package has not had a release in years. ",[73,1498,24],{}," is the maintained fork with type hints and bug fixes, and it is a drop-in replacement (",[73,1501,1502],{},"from docopt import docopt","). Use it for new code and when modernising an old project.",[1486,1505,1507],{"id":1506},"how-does-cyclopts-differ-from-typer-in-practice","How does Cyclopts differ from Typer in practice?",[10,1509,1510,1511,1513,1514,1517],{},"Both build the CLI from type hints. Cyclopts supports more types natively (unions, ",[73,1512,75],{},", dataclasses, Pydantic models), parses help from docstrings, makes keyword-only parameters into options and positional ones into arguments, and has built-in config sources such as environment variables and TOML files. Typer builds on Click, which gives it Click's ecosystem and plugins. The ",[39,1515,1516],{"href":51},"Typer vs Click guide"," covers the Click side of that trade.",[1486,1519,1521],{"id":1520},"can-i-use-fire-for-a-quick-prototype-and-switch-later","Can I use Fire for a quick prototype and switch later?",[10,1523,1524],{},"Yes, and it is a good workflow: expose functions with Fire while the interface is still moving, then write explicit Typer or Cyclopts commands once it settles. Because Fire needs no declarations, the functions are already framework-free.",[1486,1526,1528],{"id":1527},"why-does-poetry-use-cleo-instead-of-click","Why does Poetry use Cleo instead of Click?",[10,1530,1531],{},"Cleo comes from the same author's ecosystem and models commands as classes with namespaces, verbosity levels and testers — a structure that suits an application with many commands and shared I\u002FO. It is a design preference rather than a capability gap.",[1486,1533,1535],{"id":1534},"what-about-argh-plac-clize-and-others","What about argh, plac, clize and others?",[10,1537,1538],{},"They exist and work, mostly as thin layers over argparse that derive arguments from function signatures. They are less widely used than the frameworks above, so you get less community help. Evaluate them with the same criteria: declaration model, validation, exit codes, completion and testing.",[59,1540,1542],{"id":1541},"related","Related",[64,1544,1545,1550,1555,1560,1564,1568,1575],{},[67,1546,1547,1548],{},"Up: ",[39,1549,42],{"href":41},[67,1551,1552,1553],{},"Down: ",[39,1554,1039],{"href":1038},[67,1556,1552,1557],{},[39,1558,1559],{"href":1049},"Quick CLIs from functions with Python Fire",[67,1561,1552,1562],{},[39,1563,1060],{"href":1059},[67,1565,1552,1566],{},[39,1567,1071],{"href":1070},[67,1569,1570,1571],{},"Sideways: ",[39,1572,1574],{"href":1573},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-vs-click-vs-typer-comparison\u002F","argparse vs Click vs Typer comparison",[67,1576,1570,1577],{},[39,1578,52],{"href":51},[1580,1581,1582],"style",{},"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 .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}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 .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}",{"title":174,"searchDepth":198,"depth":198,"links":1584},[1585,1586,1587,1588,1589,1590,1591,1592,1593,1594,1595,1596,1603],{"id":61,"depth":198,"text":62},{"id":100,"depth":198,"text":101},{"id":154,"depth":198,"text":155},{"id":899,"depth":198,"text":900},{"id":1017,"depth":198,"text":1018},{"id":1081,"depth":198,"text":1082},{"id":1216,"depth":198,"text":1217},{"id":1296,"depth":198,"text":1297},{"id":1351,"depth":198,"text":1352},{"id":1416,"depth":198,"text":1417},{"id":1458,"depth":198,"text":1459},{"id":1483,"depth":198,"text":1484,"children":1597},[1598,1599,1600,1601,1602],{"id":1488,"depth":211,"text":1489},{"id":1506,"depth":211,"text":1507},{"id":1520,"depth":211,"text":1521},{"id":1527,"depth":211,"text":1528},{"id":1534,"depth":211,"text":1535},{"id":1541,"depth":198,"text":1542},"2026-10-02","Cyclopts, Python Fire, docopt-ng and Cleo compared with Click and Typer: parsing models, type handling, testing, exit codes and when each is the better choice.","intermediate",false,"md",{},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks",{"title":5,"description":1605},"modern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Findex",[1614,1615,1616,1495,1617],"frameworks","cyclopts","fire","cleo","azahJne-iAptnWEJv7ycm_yGpiWHW8iCiqrbrKhvshY",[1620,1623,1626,1629,1632,1635,1638,1641,1644,1647,1650,1653,1656,1659,1662,1665,1668,1671,1674,1677,1680,1683,1686,1689,1692,1695,1698,1701,1704,1707,1710,1713,1716,1719,1722,1725,1728,1731,1734,1737,1740,1743,1746,1749,1752,1755,1758,1761,1764,1767,1770,1773,1776,1779,1782,1785,1788,1791,1794,1797,1800,1803,1806,1809,1812,1815,1818,1821,1824,1827,1830,1833,1836,1839,1842,1845,1848,1851,1854,1857,1860,1863,1866,1869,1872,1875,1878,1881,1884,1887,1890,1893,1896,1899,1902,1905,1908,1911,1914,1917,1920,1923,1926,1929,1932,1935,1938,1941,1944,1947,1950,1953,1956,1959,1962,1965,1968,1971,1974,1977,1980,1983,1986,1989,1992,1995,1998,2001,2004,2007,2010,2013,2016,2019,2022,2025,2028,2031,2034,2037,2040,2043,2046,2047,2050,2053,2056,2059,2062,2065,2068,2071,2074,2077,2080,2083,2086,2089,2092,2095,2098,2101,2104,2107,2110,2113,2116,2119,2122,2125,2128,2131,2134,2137,2140,2143,2146,2149,2152,2155,2158,2161,2164,2167,2170,2173,2176,2179,2182,2185,2188,2191,2194,2197,2200,2203,2206,2209,2212,2215,2218,2221,2224,2227,2230,2233,2236,2239,2242,2245,2248,2251,2254,2257,2260,2263,2266,2269,2272,2275,2278,2281,2284,2287,2290,2293,2296,2299,2302,2305,2308,2311,2314,2317,2320,2323,2326,2329,2332,2335,2338,2341,2344,2347,2350,2353,2356,2359,2362,2365,2368,2371,2374,2377,2380,2383,2386,2389,2392,2395,2398,2401,2404,2407,2410,2413,2416,2419,2422,2425,2428,2431,2434,2437,2440,2443,2446,2449,2452,2455,2458,2461],{"path":1621,"title":1622},"\u002Fabout","About Python CLI Toolcraft",{"path":1624,"title":1625},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies","Advanced Argument Validation Strategies",{"path":1627,"title":1628},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fparsing-nested-json-arguments-in-python-clis","Parsing Nested JSON Args in Python CLIs",{"path":1630,"title":1631},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-dates-and-durations-in-cli-arguments","Validating Dates and Durations in Python CLI Arguments",{"path":1633,"title":1634},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-dependent-and-conflicting-options","Validating Dependent and Conflicting CLI Options",{"path":1636,"title":1637},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-file-and-directory-paths-in-clis","Validating File and Directory Paths in CLIs",{"path":1639,"title":1640},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-urls-hosts-and-ports","Validating URLs, Hosts and Ports in Python CLI Arguments",{"path":1642,"title":1643},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fwriting-custom-click-parameter-types","Writing Custom Click Parameter Types",{"path":1645,"title":1646},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fbrowsing-records-with-a-textual-datatable","Browsing Records with a Textual DataTable Picker",{"path":1648,"title":1649},"\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":1651,"title":1652},"\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":1654,"title":1655},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual","Building Terminal UIs with Textual for Python CLIs",{"path":1657,"title":1658},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Frunning-background-work-in-textual-with-workers","Running Background Work in Textual with Workers",{"path":1660,"title":1661},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fstyling-textual-apps-with-tcss","Styling Textual Apps with TCSS",{"path":1663,"title":1664},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Ftesting-textual-apps-with-pilot","Testing Textual Apps with Pilot",{"path":1666,"title":1667},"\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":1669,"title":1670},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fdocumenting-environment-variables-in-help","Documenting Environment Variables in CLI Help",{"path":1672,"title":1673},"\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":1675,"title":1676},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation","CLI Help Output and Documentation",{"path":1678,"title":1679},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Frich-formatted-help-with-rich-click","Rich-Formatted Help for Click CLIs with rich-click",{"path":1681,"title":1682},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fversioning-and-deprecating-cli-flags","Versioning and Deprecating CLI Flags",{"path":1684,"title":1685},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fwriting-help-text-users-actually-read","Writing Help Text Users Actually Read",{"path":1687,"title":1688},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fadapting-output-to-terminal-width","Adapting Python CLI Output to Terminal Width",{"path":1690,"title":1691},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fdetecting-ci-environments-and-non-interactive-shells","Detecting CI Environments and Non-Interactive Shells",{"path":1693,"title":1694},"\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":1696,"title":1697},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fhandling-ansi-escape-codes-on-windows-consoles","Handling ANSI Escape Codes on Windows Consoles",{"path":1699,"title":1700},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility","Cross-Platform Terminal Compatibility for Python CLIs",{"path":1702,"title":1703},"\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":1705,"title":1706},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fsupporting-dumb-terminals-and-screen-readers","Supporting Dumb Terminals and Screen Readers in a Python CLI",{"path":1708,"title":1709},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fchoosing-exit-codes-for-cli-tools","Choosing Exit Codes for CLI Tools",{"path":1711,"title":1712},"\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":1714,"title":1715},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fdid-you-mean-suggestions-for-mistyped-input","Did You Mean…? Suggestions for Mistyped CLI Input",{"path":1717,"title":1718},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Ffriendly-error-messages-and-tracebacks","Friendly Error Messages and Tracebacks",{"path":1720,"title":1721},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fhandling-keyboard-interrupt-cleanly","Handling Keyboard Interrupt Cleanly",{"path":1723,"title":1724},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes","Error Handling and Exit Codes for CLIs",{"path":1726,"title":1727},"\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":1729,"title":1730},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fwriting-crash-reports-users-can-send","Writing Crash Reports Users Can Send",{"path":1732,"title":1733},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Fconfig-precedence-flags-env-files-defaults","Config Precedence: Flags, Env, Files, Defaults",{"path":1735,"title":1736},"\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":1738,"title":1739},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars","Handling Config Files and Env Vars in CLIs",{"path":1741,"title":1742},"\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":1744,"title":1745},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Freading-toml-config-with-tomllib","Reading TOML Config with tomllib in Python CLIs",{"path":1747,"title":1748},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Ftyped-settings-with-pydantic-settings","Typed Settings with pydantic-settings in Python CLIs",{"path":1750,"title":1751},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Fvalidating-config-files-with-json-schema","Validating Config Files with JSON Schema in a Python CLI",{"path":1753,"title":1754},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Fwriting-a-config-init-and-edit-command","Writing a Config Init and Edit Command for a Python CLI",{"path":1756,"title":1757},"\u002Fadvanced-input-parsing-user-experience","Advanced Input Parsing for Python CLIs",{"path":1759,"title":1760},"\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":1762,"title":1763},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Fbuilding-interactive-prompts-and-menus","Building Interactive Prompts and Menus in Python CLIs",{"path":1765,"title":1766},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Fbuilding-tree-views-with-rich","Building Tree Views with Rich in a Python CLI",{"path":1768,"title":1769},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich","Interactive Terminal UI with Rich",{"path":1771,"title":1772},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Flive-dashboards-with-rich-live","Live Dashboards with Rich Live in Python CLIs",{"path":1774,"title":1775},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Frendering-markdown-and-syntax-highlighting-with-rich","Rendering Markdown and Syntax Highlighting with Rich",{"path":1777,"title":1778},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Frendering-tables-and-json-with-rich","Rendering Tables and JSON with Rich",{"path":1780,"title":1781},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Ftheming-rich-output-consistently","Theming Rich Output Consistently in Python CLIs",{"path":1783,"title":1784},"\u002Fadvanced-input-parsing-user-experience\u002Foutput-formats-for-data-clis\u002Fadding-a-format-flag-for-table-json-and-csv","Adding a Format Flag for Table, JSON and CSV Output",{"path":1786,"title":1787},"\u002Fadvanced-input-parsing-user-experience\u002Foutput-formats-for-data-clis\u002Fcustom-output-templates-with-a-format-string","Custom Output Templates with a Format String in Python CLIs",{"path":1789,"title":1790},"\u002Fadvanced-input-parsing-user-experience\u002Foutput-formats-for-data-clis\u002Fexporting-cli-results-to-files","Exporting CLI Results to Files from a Python CLI",{"path":1792,"title":1793},"\u002Fadvanced-input-parsing-user-experience\u002Foutput-formats-for-data-clis","Output Formats for Data-Heavy Python CLIs",{"path":1795,"title":1796},"\u002Fadvanced-input-parsing-user-experience\u002Foutput-formats-for-data-clis\u002Fselecting-fields-and-columns-from-cli-output","Selecting Fields and Columns from Python CLI Output",{"path":1798,"title":1799},"\u002Fadvanced-input-parsing-user-experience\u002Foutput-formats-for-data-clis\u002Fwriting-csv-and-tsv-output-correctly","Writing CSV and TSV Output Correctly from a Python CLI",{"path":1801,"title":1802},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fargcomplete-for-argparse-clis","Tab Completion for argparse CLIs with argcomplete",{"path":1804,"title":1805},"\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":1807,"title":1808},"\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":1810,"title":1811},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis","Shell Completion for Python CLIs",{"path":1813,"title":1814},"\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":1816,"title":1817},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fshipping-completion-scripts-with-packages","Shipping Shell Completion Scripts with a Python CLI",{"path":1819,"title":1820},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Ftesting-shell-completion-in-python-clis","Testing Shell Completion in Python CLIs",{"path":1822,"title":1823},"\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":1825,"title":1826},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fadding-verbose-and-quiet-logging-flags","Adding Verbose and Quiet Logging Flags",{"path":1828,"title":1829},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps","Structured Logging for CLI Apps",{"path":1831,"title":1832},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Flogging-with-structlog-in-a-cli","Logging with structlog in a Python CLI",{"path":1834,"title":1835},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fseparating-logs-from-program-output","Separating Logs from Program Output in a Python CLI",{"path":1837,"title":1838},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fstructured-json-logging-in-python-clis","Structured JSON Logging in Python CLIs",{"path":1840,"title":1841},"\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":1843,"title":1844},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fdetecting-tty-and-adapting-output","Detecting a TTY and Adapting Output",{"path":1846,"title":1847},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Femitting-json-output-for-scripting","Emitting JSON Output for Scripting",{"path":1849,"title":1850},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fhandling-broken-pipe-and-sigpipe","Handling Broken Pipe and SIGPIPE",{"path":1852,"title":1853},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes","Working with stdin, stdout and Pipes",{"path":1855,"title":1856},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fnull-delimited-input-and-xargs-compatibility","Null-Delimited Input and xargs Compatibility in Python CLIs",{"path":1858,"title":1859},"\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":1861,"title":1862},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Freading-piped-input-in-python-clis","Reading Piped Input in Python CLIs",{"path":1864,"title":1865},"\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":1867,"title":1868},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fdownloading-files-with-progress-in-python","Downloading Files with Progress in Python CLIs",{"path":1870,"title":1871},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis","Calling HTTP APIs from Python CLIs",{"path":1873,"title":1874},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fmocking-http-in-cli-tests-with-respx","Mocking HTTP in Python CLI Tests with respx",{"path":1876,"title":1877},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Foauth-device-flow-login-for-clis","OAuth Device Flow Login for Python CLIs",{"path":1879,"title":1880},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fpaginating-api-results-in-a-cli","Paginating API Results in a Python CLI",{"path":1882,"title":1883},"\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":1885,"title":1886},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fuploading-files-with-multipart-and-progress","Uploading Files with Multipart and Progress in a Python CLI",{"path":1888,"title":1889},"\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":1891,"title":1892},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis","Concurrency and Async in Python CLIs",{"path":1894,"title":1895},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fmultiprocessing-for-cpu-bound-cli-tasks","Multiprocessing for CPU-Bound CLI Tasks",{"path":1897,"title":1898},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fparallelising-cli-work-with-thread-pools","Parallelising CLI Work with Thread Pools",{"path":1900,"title":1901},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Frate-limiting-concurrent-requests-in-clis","Rate-Limiting Concurrent Requests in Python CLIs",{"path":1903,"title":1904},"\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":1906,"title":1907},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fshowing-progress-for-concurrent-tasks","Showing Progress for Concurrent Tasks in a Python CLI",{"path":1909,"title":1910},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fstructured-concurrency-with-taskgroups-in-clis","Structured Concurrency with TaskGroups in Python CLIs",{"path":1912,"title":1913},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fcross-platform-paths-with-pathlib","Cross-Platform Paths with pathlib in CLIs",{"path":1915,"title":1916},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Ffile-locking-for-concurrent-cli-runs","File Locking for Concurrent CLI Runs in Python",{"path":1918,"title":1919},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fhandling-file-permissions-and-umask-in-clis","Handling File Permissions and umask in Python CLIs",{"path":1921,"title":1922},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes","Filesystem Paths and Atomic Writes for CLIs",{"path":1924,"title":1925},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fsafe-temporary-files-and-directories","Safe Temporary Files and Directories in CLIs",{"path":1927,"title":1928},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fstoring-app-data-with-platformdirs","Storing CLI App Data with platformdirs",{"path":1930,"title":1931},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fwalking-directory-trees-with-ignore-rules","Walking Directory Trees with Ignore Rules in a Python CLI",{"path":1933,"title":1934},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fwriting-files-atomically-in-python-clis","Writing Files Atomically in Python CLIs",{"path":1936,"title":1937},"\u002Fcli-runtime-systems-integration","CLI Runtime & Systems Integration for Python",{"path":1939,"title":1940},"\u002Fcli-runtime-systems-integration\u002Flocal-state-and-sqlite-in-python-clis\u002Fcaching-http-responses-on-disk-in-a-cli","Caching HTTP Responses on Disk in a Python CLI",{"path":1942,"title":1943},"\u002Fcli-runtime-systems-integration\u002Flocal-state-and-sqlite-in-python-clis","Local State and SQLite in Python CLIs",{"path":1945,"title":1946},"\u002Fcli-runtime-systems-integration\u002Flocal-state-and-sqlite-in-python-clis\u002Fmigrating-a-cli-sqlite-schema","Migrating a CLI’s SQLite Schema Between Releases",{"path":1948,"title":1949},"\u002Fcli-runtime-systems-integration\u002Flocal-state-and-sqlite-in-python-clis\u002Frecording-and-querying-cli-run-history","Recording and Querying CLI Run History in SQLite",{"path":1951,"title":1952},"\u002Fcli-runtime-systems-integration\u002Flocal-state-and-sqlite-in-python-clis\u002Fstoring-cli-state-in-sqlite","Storing CLI State in SQLite with a Small Repository Class",{"path":1954,"title":1955},"\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":1957,"title":1958},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fhandling-sigterm-and-graceful-shutdown","Handling SIGTERM and Graceful Shutdown in CLIs",{"path":1960,"title":1961},"\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":1963,"title":1964},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis","Long-Running and Watch-Mode Python CLIs",{"path":1966,"title":1967},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Freloading-config-on-sighup","Reloading Configuration on SIGHUP in a Python CLI",{"path":1969,"title":1970},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Frunning-a-cli-as-a-systemd-service","Running a Python CLI as a systemd Service",{"path":1972,"title":1973},"\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":1975,"title":1976},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fsending-cli-logs-to-journald-and-syslog","Sending Python CLI Logs to journald and syslog",{"path":1978,"title":1979},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Favoiding-shell-injection-in-python-clis","Avoiding Shell Injection in Python CLIs",{"path":1981,"title":1982},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fcalling-external-commands-safely-with-subprocess","Calling External Commands Safely with subprocess",{"path":1984,"title":1985},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fhandling-subprocess-timeouts-and-exit-codes","Handling Subprocess Timeouts and Exit Codes",{"path":1987,"title":1988},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis","Running Subprocesses from Python CLIs",{"path":1990,"title":1991},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Flaunching-the-users-editor-from-a-cli","Launching the User’s Editor from a Python CLI",{"path":1993,"title":1994},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fpiping-between-subprocesses-in-python","Piping Between Subprocesses in Python Without a Shell",{"path":1996,"title":1997},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fstreaming-subprocess-output-in-real-time","Streaming Subprocess Output in Real Time",{"path":1999,"title":2000},"\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":2002,"title":2003},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis","Secrets and Credentials in Python CLIs",{"path":2005,"title":2006},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fprompting-for-passwords-securely","Prompting for Passwords Securely in Python CLIs",{"path":2008,"title":2009},"\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":2011,"title":2012},"\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":2014,"title":2015},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Frefreshing-expired-tokens-automatically","Refreshing Expired Tokens Automatically in a Python CLI",{"path":2017,"title":2018},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fstoring-tokens-with-keyring","Storing CLI Tokens Securely with keyring",{"path":2020,"title":2021},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fsupporting-multiple-profiles-and-accounts","Supporting Multiple Profiles and Accounts in CLIs",{"path":2023,"title":2024},"\u002Fcli-runtime-systems-integration\u002Fupdate-checks-and-self-updating-clis\u002Fchecking-pypi-for-a-newer-version","Checking PyPI for a Newer Version of Your Python CLI",{"path":2026,"title":2027},"\u002Fcli-runtime-systems-integration\u002Fupdate-checks-and-self-updating-clis","Update Checks, Upgrade Commands and Telemetry for Python CLIs",{"path":2029,"title":2030},"\u002Fcli-runtime-systems-integration\u002Fupdate-checks-and-self-updating-clis\u002Fopt-in-usage-telemetry-for-python-clis","Opt-In Usage Telemetry for Python CLIs Done Responsibly",{"path":2032,"title":2033},"\u002Fcli-runtime-systems-integration\u002Fupdate-checks-and-self-updating-clis\u002Fself-upgrading-a-cli-installed-with-pipx-or-uv","Self-Upgrading a Python CLI Installed with pipx or uv",{"path":2035,"title":2036},"\u002Fcli-runtime-systems-integration\u002Fupdate-checks-and-self-updating-clis\u002Fshowing-non-blocking-update-notices","Showing Non-Blocking Update Notices in a Python CLI",{"path":2038,"title":2039},"\u002F","Python CLI Toolcraft",{"path":2041,"title":2042},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cleo","Building a Python CLI with Cleo Command Classes",{"path":2044,"title":2045},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cyclopts","Building a Type-Hinted Python CLI with Cyclopts",{"path":1610,"title":5},{"path":2048,"title":2049},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fquick-clis-from-functions-with-python-fire","Quick CLIs from Functions with Python Fire",{"path":2051,"title":2052},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fusage-string-driven-clis-with-docopt-ng","Usage-String Driven Python CLIs with docopt-ng",{"path":2054,"title":2055},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Favoiding-import-time-side-effects","Avoiding Import-Time Side Effects in a Python CLI",{"path":2057,"title":2058},"\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":2060,"title":2061},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fguarding-startup-with-import-tests","Guarding CLI Startup with Import Tests",{"path":2063,"title":2064},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading","CLI Startup Performance and Lazy Loading",{"path":2066,"title":2067},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Flazy-loading-subcommands-for-faster-startup","Lazy Loading Subcommands for Faster Startup",{"path":2069,"title":2070},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fprofiling-python-cli-startup-time","Profiling Python CLI Startup Time",{"path":2072,"title":2073},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Freducing-cli-dependency-weight","Reducing CLI Dependency Weight",{"path":2075,"title":2076},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-subparsers-for-subcommands","argparse Subparsers for Subcommands",{"path":2078,"title":2079},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-vs-click-vs-typer-comparison","argparse vs Click vs Typer Compared",{"path":2081,"title":2082},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargument-groups-and-help-formatting-in-argparse","Argument Groups and Help Formatting in argparse",{"path":2084,"title":2085},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse","Command-Line Parsing with argparse",{"path":2087,"title":2088},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmigrating-from-argparse-to-typer","Migrating from argparse to Typer",{"path":2090,"title":2091},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmutually-exclusive-options-in-argparse","Mutually Exclusive Options in argparse",{"path":2093,"title":2094},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Freading-arguments-from-files-with-fromfile-prefix-chars","Reading Arguments from Files with argparse’s fromfile_prefix_chars",{"path":2096,"title":2097},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fwriting-custom-argparse-actions","Writing Custom argparse Actions in Python",{"path":2099,"title":2100},"\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":2102,"title":2103},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fdesigning-idempotent-commands","Designing Idempotent Commands in a Python CLI",{"path":2105,"title":2106},"\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":2108,"title":2109},"\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":2111,"title":2112},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions","Designing CLI Interfaces and Conventions in Python",{"path":2114,"title":2115},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fnaming-commands-and-flags-consistently","Naming Commands and Flags Consistently in Python CLIs",{"path":2117,"title":2118},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fpositional-arguments-vs-options","Positional Arguments vs Options: Designing a CLI Signature",{"path":2120,"title":2121},"\u002Fmodern-python-cli-frameworks-architecture","Python CLI Frameworks and Architecture",{"path":2123,"title":2124},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fdiscovering-plugins-with-entry-points","Discovering Plugins with Entry Points in Python CLIs",{"path":2126,"title":2127},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fhook-based-plugins-with-pluggy","Hook-Based Plugins for Python CLIs with pluggy",{"path":2129,"title":2130},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis","Plugin Architectures for Extensible CLIs",{"path":2132,"title":2133},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fisolating-plugin-failures","Isolating Plugin Failures in an Extensible Python CLI",{"path":2135,"title":2136},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Ftesting-plugins-against-the-host-cli","Testing Plugins Against the Host CLI",{"path":2138,"title":2139},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fversioning-a-plugin-api","Versioning a Plugin API for a Python CLI",{"path":2141,"title":2142},"\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":2144,"title":2145},"\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":2147,"title":2148},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fdependency-injection-patterns-for-cli-commands","Dependency Injection Patterns for CLI Commands",{"path":2150,"title":2151},"\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":2153,"title":2154},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis","Structuring Multi-Command Python CLIs",{"path":2156,"title":2157},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Foffering-a-python-api-alongside-your-cli","Offering a Python API Alongside Your CLI",{"path":2159,"title":2160},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fregistering-commands-from-modules-automatically","Registering CLI Commands from Modules Automatically",{"path":2162,"title":2163},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-common-options-across-commands","Sharing Common Options Across Python CLI Commands",{"path":2165,"title":2166},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-state-with-click-context-objects","Sharing State with Click Context Objects",{"path":2168,"title":2169},"\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":2171,"title":2172},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications","Testing Python CLI Applications",{"path":2174,"title":2175},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fmeasuring-cli-test-coverage","Measuring CLI Test Coverage",{"path":2177,"title":2178},"\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":2180,"title":2181},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fproperty-based-testing-cli-arguments-with-hypothesis","Property-Based Testing CLI Arguments with Hypothesis",{"path":2183,"title":2184},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fsnapshot-testing-cli-output","Snapshot Testing CLI Output",{"path":2186,"title":2187},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-click-commands-with-clirunner","Testing Click Commands with CliRunner",{"path":2189,"title":2190},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-commands-that-call-subprocesses","Testing Python CLI Commands That Call Subprocesses",{"path":2192,"title":2193},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-interactive-prompts-and-stdin","Testing Interactive Prompts and stdin",{"path":2195,"title":2196},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftranscript-tests-for-cli-commands","Transcript Tests for Python CLI Commands",{"path":2198,"title":2199},"\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":2201,"title":2202},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fbuilding-dynamic-commands-in-click","Building Dynamic Commands in Click",{"path":2204,"title":2205},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fchoices-and-enums-in-typer-and-click","Choices and Enums in Typer and Click Options",{"path":2207,"title":2208},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fclick-option-callbacks-and-eager-options","Click Option Callbacks and Eager Options Explained",{"path":2210,"title":2211},"\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":2213,"title":2214},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each","Typer vs Click: When to Use Each",{"path":2216,"title":2217},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Frich-markup-and-help-panels-in-typer","Rich Markup and Help Panels in Typer",{"path":2219,"title":2220},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Ftyper-callback-functions-explained","Typer callback functions explained",{"path":2222,"title":2223},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fusing-annotated-options-in-typer","Using Annotated Options in Typer",{"path":2225,"title":2226},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fautomating-releases-from-git-tags","Automating Python CLI Releases from Git Tags",{"path":2228,"title":2229},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fcaching-uv-dependencies-in-ci","Caching uv Dependencies in CI for Python CLIs",{"path":2231,"title":2232},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis","CI\u002FCD Pipelines for Python CLIs",{"path":2234,"title":2235},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fpublishing-a-cli-docker-image-from-ci","Publishing a Python CLI as a Docker Image from CI",{"path":2237,"title":2238},"\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":2240,"title":2241},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Frunning-cli-tests-on-windows-and-macos-runners","Running Python CLI Tests on Windows and macOS Runners",{"path":2243,"title":2244},"\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":2246,"title":2247},"\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":2249,"title":2250},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fbuilding-a-cookiecutter-template-for-typer-clis","Building a Cookiecutter Template for Typer CLIs",{"path":2252,"title":2253},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fcopier-vs-cookiecutter-for-cli-templates","Copier vs Cookiecutter for CLI Templates",{"path":2255,"title":2256},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter","CLI Project Scaffolding with Cookiecutter",{"path":2258,"title":2259},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fpost-generation-hooks-in-cli-templates","Post-Generation Hooks in Python CLI Templates",{"path":2261,"title":2262},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftemplate-variables-and-conditional-files","Template Variables and Conditional Files in CLI Templates",{"path":2264,"title":2265},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftesting-a-project-template-with-pytest","Testing a CLI Project Template with pytest",{"path":2267,"title":2268},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fupdating-generated-projects-with-copier-update","Updating Generated CLI Projects with copier update",{"path":2270,"title":2271},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbuilding-cross-platform-release-binaries-in-ci","Building Cross-Platform Release Binaries in CI",{"path":2273,"title":2274},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbundling-a-python-cli-with-pyinstaller","Bundling a Python CLI with PyInstaller",{"path":2276,"title":2277},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fcode-signing-and-notarizing-cli-binaries","Code Signing and Notarizing Python CLI Binaries",{"path":2279,"title":2280},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fhomebrew-and-scoop-packaging-for-python-clis","Homebrew and Scoop Packaging for Python CLIs",{"path":2282,"title":2283},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries","Distributing CLIs as Standalone Binaries",{"path":2285,"title":2286},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fnuitka-vs-pyinstaller-for-python-clis","Nuitka vs PyInstaller for Python CLI Binaries",{"path":2288,"title":2289},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Freducing-pyinstaller-binary-size","Reducing the Size of a PyInstaller CLI Binary",{"path":2291,"title":2292},"\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":2294,"title":2295},"\u002Fproject-setup-dependency-management","Project Setup & Dependency Management",{"path":2297,"title":2298},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fconfiguring-ruff-for-a-cli-project","Configuring Ruff for a Python CLI Project",{"path":2300,"title":2301},"\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":2303,"title":2304},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Ffinding-unused-code-and-dependencies-with-vulture-and-deptry","Finding Unused Code and Dependencies with vulture and deptry",{"path":2306,"title":2307},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code","Linting and Type-Checking Python CLI Code",{"path":2309,"title":2310},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Frunning-pyright-in-strict-mode-on-a-cli","Running Pyright in Strict Mode on a Python CLI",{"path":2312,"title":2313},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Frunning-ruff-and-mypy-in-ci-with-annotations","Running Ruff and mypy in CI with Inline Annotations",{"path":2315,"title":2316},"\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":2318,"title":2319},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fautomating-changelogs-with-conventional-commits","Automating Changelogs with Conventional Commits",{"path":2321,"title":2322},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fbumping-versions-consistently-across-a-cli-project","Bumping Versions Consistently Across a Python CLI Project",{"path":2324,"title":2325},"\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":2327,"title":2328},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fexposing-version-info-and-build-metadata","Exposing Version Info and Build Metadata",{"path":2330,"title":2331},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs","Managing CLI Versioning & Changelogs",{"path":2333,"title":2334},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fsemantic-versioning-policy-for-cli-tools","A Semantic Versioning Policy for CLI Tools",{"path":2336,"title":2337},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fshipping-pre-releases-and-release-candidates","Shipping Pre-Releases and Release Candidates of a Python CLI",{"path":2339,"title":2340},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbuilding-wheels-and-sdists-for-python-clis","Building Wheels and sdists for Python CLIs",{"path":2342,"title":2343},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbundling-data-files-with-importlib-resources","Bundling Data Files with importlib.resources in CLIs",{"path":2345,"title":2346},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fchoosing-a-build-backend-for-a-python-cli","Choosing a Build Backend for a Python CLI",{"path":2348,"title":2349},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution","Packaging Python CLIs for Distribution",{"path":2351,"title":2352},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Finstalling-and-distributing-clis-with-pipx","Installing and Distributing CLIs with pipx",{"path":2354,"title":2355},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Foptional-dependencies-and-extras-for-clis","Optional Dependencies and Extras for Python CLIs",{"path":2357,"title":2358},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fpublishing-a-python-cli-to-pypi","Publishing a Python CLI to PyPI",{"path":2360,"title":2361},"\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":2363,"title":2364},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fdynamic-versioning-with-poetry-plugins","Dynamic Versioning for a Poetry CLI from Git Tags",{"path":2366,"title":2367},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development","Poetry Workflows for CLI Development",{"path":2369,"title":2370},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fmanaging-poetry-lock-files-for-cli-tools","Managing Poetry Lock Files for CLI Tools",{"path":2372,"title":2373},"\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":2375,"title":2376},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-dependency-groups-for-cli-tooling","Poetry Dependency Groups for CLI Tooling",{"path":2378,"title":2379},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-entry-points-and-scripts-for-clis","Poetry Entry Points and Scripts for CLIs",{"path":2381,"title":2382},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpublishing-a-cli-with-poetry","Building and Publishing a Python CLI with Poetry",{"path":2384,"title":2385},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects","Pre-commit Hooks for CLI Projects",{"path":2387,"title":2388},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects\u002Fkeeping-hook-versions-current-with-autoupdate","Keeping pre-commit Hook Versions Current with autoupdate",{"path":2390,"title":2391},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects\u002Frunning-pre-commit-in-ci","Running pre-commit in CI for a Python CLI Repository",{"path":2393,"title":2394},"\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":2396,"title":2397},"\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":2399,"title":2400},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects\u002Fspeeding-up-slow-pre-commit-hooks","Speeding Up Slow pre-commit Hooks in a CLI Repository",{"path":2402,"title":2403},"\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":2405,"title":2406},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fauditing-dependencies-with-pip-audit","Auditing a Python CLI’s Dependencies with pip-audit",{"path":2408,"title":2409},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fgenerating-an-sbom-for-a-python-cli","Generating an SBOM for a Python CLI Release",{"path":2411,"title":2412},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain","Securing the Supply Chain of a Python CLI",{"path":2414,"title":2415},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpinning-dependencies-with-hashes","Pinning a Python CLI’s Dependencies with Hashes",{"path":2417,"title":2418},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpublishing-attestations-and-verifying-releases","Publishing Attestations and Verifying Python CLI Releases",{"path":2420,"title":2421},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fbuilding-and-publishing-a-cli-with-uv","Building and Publishing a Python CLI with uv",{"path":2423,"title":2424},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management","uv for Python CLI Dependency Management",{"path":2426,"title":2427},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Flocking-and-syncing-cli-dependencies-with-uv","Locking and Syncing a Python CLI’s Dependencies with uv",{"path":2429,"title":2430},"\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":2432,"title":2433},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fusing-private-package-indexes-with-uv","Using Private Package Indexes with uv for Internal CLIs",{"path":2435,"title":2436},"\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":2438,"title":2439},"\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":2441,"title":2442},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis","uv Workspaces for Multi-Package Python CLIs",{"path":2444,"title":2445},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fdebugging-wrong-python-and-wrong-venv-problems","Debugging Wrong-Python and Wrong-Venv Problems in CLIs",{"path":2447,"title":2448},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fexternally-managed-environments-and-pep-668","PEP 668 and Python CLIs: the externally-managed-environment Error",{"path":2450,"title":2451},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices","Python CLI Env Isolation Best Practices",{"path":2453,"title":2454},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fisolating-cli-tools-from-project-dependencies","Isolating CLI Tools from Your Project’s Dependencies",{"path":2456,"title":2457},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fmanaging-virtual-environments-for-cross-platform-clis","Managing Python CLI Virtual Environments",{"path":2459,"title":2460},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fpinning-the-python-version-for-a-cli","Pinning the Python Version for a CLI",{"path":2462,"title":2463},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fsupporting-multiple-python-versions-with-nox","Supporting Multiple Python Versions with nox",1790967540166]