[{"data":1,"prerenderedAt":2236},["ShallowReactive",2],{"page-\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fdependency-injection-patterns-for-cli-commands\u002F":3,"content-directory":1392},{"id":4,"title":5,"body":6,"date":1376,"description":1377,"difficulty":1378,"draft":1379,"extension":1380,"meta":1381,"navigation":121,"path":1382,"seo":1383,"stem":1384,"tags":1385,"updated":1376,"__hash__":1391},"content\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fdependency-injection-patterns-for-cli-commands\u002Findex.md","Dependency Injection Patterns for CLI Commands",{"type":7,"value":8,"toc":1356},"minimark",[9,13,18,57,61,70,74,78,81,275,347,450,462,466,469,475,481,563,566,572,578,582,585,590,676,821,832,836,839,842,849,852,856,859,873,883,887,890,1008,1128,1142,1146,1149,1155,1218,1224,1233,1236,1239,1243,1246,1250,1255,1262,1266,1275,1279,1288,1292,1295,1299,1314,1318,1352],[10,11,12],"p",{},"Commands need things: an HTTP client, a database session, a clock, a settings object. How those\narrive decides whether your logic can be tested without patching, and whether two commands can\ndisagree about the state of the world. The answer is not a framework — it is two small habits.",[14,15,17],"h2",{"id":16},"tldr","TL;DR",[19,20,21,30,42,51,54],"ul",{},[22,23,24,25,29],"li",{},"Build collaborators ",[26,27,28],"strong",{},"once at the boundary",", put them on the context, pass them down explicitly.",[22,31,32,33,36,37,41],{},"A ",[26,34,35],{},"default parameter"," (",[38,39,40],"code",{},"client: Client | None = None",") covers most cases with no ceremony.",[22,43,44,45,50],{},"Describe the seam with a ",[26,46,47],{},[38,48,49],{},"Protocol"," so a fake cannot silently drift from the real thing.",[22,52,53],{},"Never reach for a module-level global — it is the thing tests have to remember to reset.",[22,55,56],{},"If you need a container, keep it dumb: a frozen dataclass of already-built objects.",[14,58,60],{"id":59},"prerequisites","Prerequisites",[10,62,63,64,69],{},"A CLI with the layering from\n",[65,66,68],"a",{"href":67},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002F","structuring multi-command Python CLIs",":\ncommand functions that call plain functions in a core package.",[14,71,73],{"id":72},"where-things-get-constructed","Where things get constructed",[75,76],"inline-diagram",{"name":77},"di-wiring-flow",[10,79,80],{},"The rule: construct at the boundary, once per invocation, from settings. Commands receive what they\nneed; core functions take it as arguments.",[82,83,88],"pre",{"className":84,"code":85,"language":86,"meta":87,"style":87},"language-python shiki shiki-themes github-light github-dark","# src\u002Fmytool\u002Fcontext.py\nfrom dataclasses import dataclass\n\n@dataclass(frozen=True, slots=True)\nclass Services:\n    settings: Settings\n    bucket: BucketClient\n    clock: Callable[[], datetime]\n\ndef build(settings: Settings) -> Services:\n    return Services(\n        settings=settings,\n        bucket=S3Bucket(region=settings.region, retries=settings.retries),\n        clock=lambda: datetime.now(UTC),\n    )\n","python","",[38,89,90,99,116,123,157,169,175,181,187,192,204,213,224,251,269],{"__ignoreMap":87},[91,92,95],"span",{"class":93,"line":94},"line",1,[91,96,98],{"class":97},"sJ8bj","# src\u002Fmytool\u002Fcontext.py\n",[91,100,102,106,110,113],{"class":93,"line":101},2,[91,103,105],{"class":104},"szBVR","from",[91,107,109],{"class":108},"sVt8B"," dataclasses ",[91,111,112],{"class":104},"import",[91,114,115],{"class":108}," dataclass\n",[91,117,119],{"class":93,"line":118},3,[91,120,122],{"emptyLinePlaceholder":121},true,"\n",[91,124,126,130,133,137,140,144,147,150,152,154],{"class":93,"line":125},4,[91,127,129],{"class":128},"sScJk","@dataclass",[91,131,132],{"class":108},"(",[91,134,136],{"class":135},"s4XuR","frozen",[91,138,139],{"class":104},"=",[91,141,143],{"class":142},"sj4cs","True",[91,145,146],{"class":108},", ",[91,148,149],{"class":135},"slots",[91,151,139],{"class":104},[91,153,143],{"class":142},[91,155,156],{"class":108},")\n",[91,158,160,163,166],{"class":93,"line":159},5,[91,161,162],{"class":104},"class",[91,164,165],{"class":128}," Services",[91,167,168],{"class":108},":\n",[91,170,172],{"class":93,"line":171},6,[91,173,174],{"class":108},"    settings: Settings\n",[91,176,178],{"class":93,"line":177},7,[91,179,180],{"class":108},"    bucket: BucketClient\n",[91,182,184],{"class":93,"line":183},8,[91,185,186],{"class":108},"    clock: Callable[[], datetime]\n",[91,188,190],{"class":93,"line":189},9,[91,191,122],{"emptyLinePlaceholder":121},[91,193,195,198,201],{"class":93,"line":194},10,[91,196,197],{"class":104},"def",[91,199,200],{"class":128}," build",[91,202,203],{"class":108},"(settings: Settings) -> Services:\n",[91,205,207,210],{"class":93,"line":206},11,[91,208,209],{"class":104},"    return",[91,211,212],{"class":108}," Services(\n",[91,214,216,219,221],{"class":93,"line":215},12,[91,217,218],{"class":135},"        settings",[91,220,139],{"class":104},[91,222,223],{"class":108},"settings,\n",[91,225,227,230,232,235,238,240,243,246,248],{"class":93,"line":226},13,[91,228,229],{"class":135},"        bucket",[91,231,139],{"class":104},[91,233,234],{"class":108},"S3Bucket(",[91,236,237],{"class":135},"region",[91,239,139],{"class":104},[91,241,242],{"class":108},"settings.region, ",[91,244,245],{"class":135},"retries",[91,247,139],{"class":104},[91,249,250],{"class":108},"settings.retries),\n",[91,252,254,257,260,263,266],{"class":93,"line":253},14,[91,255,256],{"class":135},"        clock",[91,258,259],{"class":104},"=lambda",[91,261,262],{"class":108},": datetime.now(",[91,264,265],{"class":142},"UTC",[91,267,268],{"class":108},"),\n",[91,270,272],{"class":93,"line":271},15,[91,273,274],{"class":108},"    )\n",[82,276,278],{"className":84,"code":277,"language":86,"meta":87,"style":87},"# src\u002Fmytool\u002Fcli.py\n@app.callback()\ndef main(ctx: typer.Context, config: Path | None = None) -> None:\n    settings = load_settings(config)\n    configure_logging(settings.verbosity)\n    ctx.obj = build(settings)\n",[38,279,280,285,293,322,332,337],{"__ignoreMap":87},[91,281,282],{"class":93,"line":94},[91,283,284],{"class":97},"# src\u002Fmytool\u002Fcli.py\n",[91,286,287,290],{"class":93,"line":101},[91,288,289],{"class":128},"@app.callback",[91,291,292],{"class":108},"()\n",[91,294,295,297,300,303,306,309,312,314,317,320],{"class":93,"line":118},[91,296,197],{"class":104},[91,298,299],{"class":128}," main",[91,301,302],{"class":108},"(ctx: typer.Context, config: Path ",[91,304,305],{"class":104},"|",[91,307,308],{"class":142}," None",[91,310,311],{"class":104}," =",[91,313,308],{"class":142},[91,315,316],{"class":108},") -> ",[91,318,319],{"class":142},"None",[91,321,168],{"class":108},[91,323,324,327,329],{"class":93,"line":125},[91,325,326],{"class":108},"    settings ",[91,328,139],{"class":104},[91,330,331],{"class":108}," load_settings(config)\n",[91,333,334],{"class":93,"line":159},[91,335,336],{"class":108},"    configure_logging(settings.verbosity)\n",[91,338,339,342,344],{"class":93,"line":171},[91,340,341],{"class":108},"    ctx.obj ",[91,343,139],{"class":104},[91,345,346],{"class":108}," build(settings)\n",[82,348,350],{"className":84,"code":349,"language":86,"meta":87,"style":87},"# src\u002Fmytool\u002Fcommands\u002Fsync.py\n@app.command()\ndef sync(ctx: typer.Context, source: Path, dry_run: bool = False) -> None:\n    services = ctx.obj\n    result = core.sync_directory(source, bucket=services.bucket, dry_run=dry_run)\n    typer.echo(f\"{result.uploaded} uploaded\")\n",[38,351,352,357,364,388,398,424],{"__ignoreMap":87},[91,353,354],{"class":93,"line":94},[91,355,356],{"class":97},"# src\u002Fmytool\u002Fcommands\u002Fsync.py\n",[91,358,359,362],{"class":93,"line":101},[91,360,361],{"class":128},"@app.command",[91,363,292],{"class":108},[91,365,366,368,371,374,377,379,382,384,386],{"class":93,"line":118},[91,367,197],{"class":104},[91,369,370],{"class":128}," sync",[91,372,373],{"class":108},"(ctx: typer.Context, source: Path, dry_run: ",[91,375,376],{"class":142},"bool",[91,378,311],{"class":104},[91,380,381],{"class":142}," False",[91,383,316],{"class":108},[91,385,319],{"class":142},[91,387,168],{"class":108},[91,389,390,393,395],{"class":93,"line":125},[91,391,392],{"class":108},"    services ",[91,394,139],{"class":104},[91,396,397],{"class":108}," ctx.obj\n",[91,399,400,403,405,408,411,413,416,419,421],{"class":93,"line":159},[91,401,402],{"class":108},"    result ",[91,404,139],{"class":104},[91,406,407],{"class":108}," core.sync_directory(source, ",[91,409,410],{"class":135},"bucket",[91,412,139],{"class":104},[91,414,415],{"class":108},"services.bucket, ",[91,417,418],{"class":135},"dry_run",[91,420,139],{"class":104},[91,422,423],{"class":108},"dry_run)\n",[91,425,426,429,432,436,439,442,445,448],{"class":93,"line":171},[91,427,428],{"class":108},"    typer.echo(",[91,430,431],{"class":104},"f",[91,433,435],{"class":434},"sZZnC","\"",[91,437,438],{"class":142},"{",[91,440,441],{"class":108},"result.uploaded",[91,443,444],{"class":142},"}",[91,446,447],{"class":434}," uploaded\"",[91,449,156],{"class":108},[10,451,452,453,457,458,461],{},"Three properties fall out. Every command sees the ",[454,455,456],"em",{},"same"," client, built once — no connection pool\nper command, no duplicated configuration parsing. The construction is in one reviewable function.\nAnd a test can build a ",[38,459,460],{},"Services"," with fakes and hand it straight to the command.",[14,463,465],{"id":464},"four-ways-to-supply-a-dependency","Four ways to supply a dependency",[75,467],{"name":468},"di-approach-matrix",[10,470,471,474],{},[26,472,473],{},"A module-level global"," is what people reach for first and the only one that is simply wrong. It\nsurvives between tests, so a suite passes or fails depending on order, and every test that touches\nit needs to remember a reset.",[10,476,477,480],{},[26,478,479],{},"A default parameter"," is the lightest thing that works, and it covers most core functions:",[82,482,484],{"className":84,"code":483,"language":86,"meta":87,"style":87},"def sync_directory(\n    source: Path,\n    *,\n    bucket: BucketClient | None = None,\n    dry_run: bool = False,\n) -> SyncResult:\n    bucket = bucket or S3Bucket()\n    ...\n",[38,485,486,496,501,509,524,537,542,558],{"__ignoreMap":87},[91,487,488,490,493],{"class":93,"line":94},[91,489,197],{"class":104},[91,491,492],{"class":128}," sync_directory",[91,494,495],{"class":108},"(\n",[91,497,498],{"class":93,"line":101},[91,499,500],{"class":108},"    source: Path,\n",[91,502,503,506],{"class":93,"line":118},[91,504,505],{"class":104},"    *",[91,507,508],{"class":108},",\n",[91,510,511,514,516,518,520,522],{"class":93,"line":125},[91,512,513],{"class":108},"    bucket: BucketClient ",[91,515,305],{"class":104},[91,517,308],{"class":142},[91,519,311],{"class":104},[91,521,308],{"class":142},[91,523,508],{"class":108},[91,525,526,529,531,533,535],{"class":93,"line":159},[91,527,528],{"class":108},"    dry_run: ",[91,530,376],{"class":142},[91,532,311],{"class":104},[91,534,381],{"class":142},[91,536,508],{"class":108},[91,538,539],{"class":93,"line":171},[91,540,541],{"class":108},") -> SyncResult:\n",[91,543,544,547,549,552,555],{"class":93,"line":177},[91,545,546],{"class":108},"    bucket ",[91,548,139],{"class":104},[91,550,551],{"class":108}," bucket ",[91,553,554],{"class":104},"or",[91,556,557],{"class":108}," S3Bucket()\n",[91,559,560],{"class":93,"line":183},[91,561,562],{"class":142},"    ...\n",[10,564,565],{},"Production code calls it with no extra argument; a test passes a fake. No patching, no container,\nand the signature documents the dependency.",[10,567,568,571],{},[26,569,570],{},"A context object"," is the right answer when several commands share the same collaborators, which\nis the usual case for a CLI. It is the pattern shown above.",[10,573,574,577],{},[26,575,576],{},"A container"," — a registry that constructs objects on demand — earns its place only when there\nare many interdependent parts with real lifecycles. For a CLI, a frozen dataclass of already-built\nobjects gives you the same benefit without the indirection.",[14,579,581],{"id":580},"making-the-seam-explicit","Making the seam explicit",[75,583],{"name":584},"di-protocol-boundary",[10,586,32,587,589],{},[38,588,49],{}," documents what a collaborator must provide, and lets a type checker verify that both\nthe real implementation and the test fake satisfy it:",[82,591,593],{"className":84,"code":592,"language":86,"meta":87,"style":87},"from typing import Protocol\n\nclass BucketClient(Protocol):\n    def is_current(self, path: Path) -> bool: ...\n    def upload(self, path: Path, *, retries: int = 3) -> None: ...\n",[38,594,595,607,611,625,644],{"__ignoreMap":87},[91,596,597,599,602,604],{"class":93,"line":94},[91,598,105],{"class":104},[91,600,601],{"class":108}," typing ",[91,603,112],{"class":104},[91,605,606],{"class":108}," Protocol\n",[91,608,609],{"class":93,"line":101},[91,610,122],{"emptyLinePlaceholder":121},[91,612,613,615,618,620,622],{"class":93,"line":118},[91,614,162],{"class":104},[91,616,617],{"class":128}," BucketClient",[91,619,132],{"class":108},[91,621,49],{"class":128},[91,623,624],{"class":108},"):\n",[91,626,627,630,633,636,638,641],{"class":93,"line":125},[91,628,629],{"class":104},"    def",[91,631,632],{"class":128}," is_current",[91,634,635],{"class":108},"(self, path: Path) -> ",[91,637,376],{"class":142},[91,639,640],{"class":108},": ",[91,642,643],{"class":142},"...\n",[91,645,646,648,651,654,657,660,663,665,668,670,672,674],{"class":93,"line":159},[91,647,629],{"class":104},[91,649,650],{"class":128}," upload",[91,652,653],{"class":108},"(self, path: Path, ",[91,655,656],{"class":104},"*",[91,658,659],{"class":108},", retries: ",[91,661,662],{"class":142},"int",[91,664,311],{"class":104},[91,666,667],{"class":142}," 3",[91,669,316],{"class":108},[91,671,319],{"class":142},[91,673,640],{"class":108},[91,675,643],{"class":142},[82,677,679],{"className":84,"code":678,"language":86,"meta":87,"style":87},"class FakeBucket:                      # no inheritance needed\n    def __init__(self) -> None:\n        self.uploaded: list[str] = []\n        self.current: set[str] = set()\n\n    def is_current(self, path: Path) -> bool:\n        return str(path) in self.current\n\n    def upload(self, path: Path, *, retries: int = 3) -> None:\n        self.uploaded.append(str(path))\n",[38,680,681,694,708,727,745,749,761,781,785,809],{"__ignoreMap":87},[91,682,683,685,688,691],{"class":93,"line":94},[91,684,162],{"class":104},[91,686,687],{"class":128}," FakeBucket",[91,689,690],{"class":108},":                      ",[91,692,693],{"class":97},"# no inheritance needed\n",[91,695,696,698,701,704,706],{"class":93,"line":101},[91,697,629],{"class":104},[91,699,700],{"class":142}," __init__",[91,702,703],{"class":108},"(self) -> ",[91,705,319],{"class":142},[91,707,168],{"class":108},[91,709,710,713,716,719,722,724],{"class":93,"line":118},[91,711,712],{"class":142},"        self",[91,714,715],{"class":108},".uploaded: list[",[91,717,718],{"class":142},"str",[91,720,721],{"class":108},"] ",[91,723,139],{"class":104},[91,725,726],{"class":108}," []\n",[91,728,729,731,734,736,738,740,743],{"class":93,"line":125},[91,730,712],{"class":142},[91,732,733],{"class":108},".current: set[",[91,735,718],{"class":142},[91,737,721],{"class":108},[91,739,139],{"class":104},[91,741,742],{"class":142}," set",[91,744,292],{"class":108},[91,746,747],{"class":93,"line":159},[91,748,122],{"emptyLinePlaceholder":121},[91,750,751,753,755,757,759],{"class":93,"line":171},[91,752,629],{"class":104},[91,754,632],{"class":128},[91,756,635],{"class":108},[91,758,376],{"class":142},[91,760,168],{"class":108},[91,762,763,766,769,772,775,778],{"class":93,"line":177},[91,764,765],{"class":104},"        return",[91,767,768],{"class":142}," str",[91,770,771],{"class":108},"(path) ",[91,773,774],{"class":104},"in",[91,776,777],{"class":142}," self",[91,779,780],{"class":108},".current\n",[91,782,783],{"class":93,"line":183},[91,784,122],{"emptyLinePlaceholder":121},[91,786,787,789,791,793,795,797,799,801,803,805,807],{"class":93,"line":189},[91,788,629],{"class":104},[91,790,650],{"class":128},[91,792,653],{"class":108},[91,794,656],{"class":104},[91,796,659],{"class":108},[91,798,662],{"class":142},[91,800,311],{"class":104},[91,802,667],{"class":142},[91,804,316],{"class":108},[91,806,319],{"class":142},[91,808,168],{"class":108},[91,810,811,813,816,818],{"class":93,"line":194},[91,812,712],{"class":142},[91,814,815],{"class":108},".uploaded.append(",[91,817,718],{"class":142},[91,819,820],{"class":108},"(path))\n",[10,822,823,824,827,828,831],{},"The value arrives when the real interface changes. Adding a method to ",[38,825,826],{},"S3Bucket"," without adding it\nto the protocol is fine; adding it to the protocol without updating the fake is a ",[38,829,830],{},"mypy"," error in\nthe pull request that made the change, rather than a runtime surprise months later.",[14,833,835],{"id":834},"what-not-to-inject","What not to inject",[10,837,838],{},"Injection is a tool for things that are slow, stateful or non-deterministic. Injecting everything\nproduces signatures nobody can read.",[10,840,841],{},"Worth injecting: HTTP clients, database sessions, filesystem roots, the clock, random sources,\nanything that talks to a service.",[10,843,844,845,848],{},"Not worth injecting: pure functions, formatting helpers, constants, standard library modules that\ndo not touch the world. ",[38,846,847],{},"json.dumps"," does not need to arrive as a parameter.",[10,850,851],{},"The test is whether a test would want to substitute it. If no test ever would, a plain import is\nclearer.",[14,853,855],{"id":854},"ux-considerations","UX considerations",[10,857,858],{},"This is an internal pattern, but it shows up in two user-visible ways.",[10,860,861,864,865,868,869,872],{},[26,862,863],{},"Start-up cost."," Building collaborators in the callback means constructing them on ",[454,866,867],{},"every","\ninvocation, including ",[38,870,871],{},"--help",". If a client opens a connection or reads credentials eagerly, that\ncost lands on the cheapest commands. Construct lazily inside the object, or build only what the\nchosen command needs.",[10,874,875,878,879,882],{},[26,876,877],{},"Error timing."," Failing to construct a client in the callback means ",[38,880,881],{},"mytool --help"," fails when\nthe configuration is wrong. Validate configuration there, but defer anything that can fail for\nenvironmental reasons — a missing credential should surface when a command needs it, with a message\nabout that command.",[14,884,886],{"id":885},"testing-the-behaviour","Testing the behaviour",[10,888,889],{},"The payoff is that tests need no patching at all:",[82,891,893],{"className":84,"code":892,"language":86,"meta":87,"style":87},"def test_sync_skips_current_files(tmp_path):\n    (tmp_path \u002F \"a.txt\").write_text(\"x\")\n    bucket = FakeBucket()\n    bucket.current.add(str(tmp_path \u002F \"a.txt\"))\n\n    result = core.sync_directory(tmp_path, bucket=bucket)\n\n    assert result == SyncResult(uploaded=0, skipped=1)\n",[38,894,895,905,924,933,950,954,970,974],{"__ignoreMap":87},[91,896,897,899,902],{"class":93,"line":94},[91,898,197],{"class":104},[91,900,901],{"class":128}," test_sync_skips_current_files",[91,903,904],{"class":108},"(tmp_path):\n",[91,906,907,910,913,916,919,922],{"class":93,"line":101},[91,908,909],{"class":108},"    (tmp_path ",[91,911,912],{"class":104},"\u002F",[91,914,915],{"class":434}," \"a.txt\"",[91,917,918],{"class":108},").write_text(",[91,920,921],{"class":434},"\"x\"",[91,923,156],{"class":108},[91,925,926,928,930],{"class":93,"line":118},[91,927,546],{"class":108},[91,929,139],{"class":104},[91,931,932],{"class":108}," FakeBucket()\n",[91,934,935,938,940,943,945,947],{"class":93,"line":125},[91,936,937],{"class":108},"    bucket.current.add(",[91,939,718],{"class":142},[91,941,942],{"class":108},"(tmp_path ",[91,944,912],{"class":104},[91,946,915],{"class":434},[91,948,949],{"class":108},"))\n",[91,951,952],{"class":93,"line":159},[91,953,122],{"emptyLinePlaceholder":121},[91,955,956,958,960,963,965,967],{"class":93,"line":171},[91,957,402],{"class":108},[91,959,139],{"class":104},[91,961,962],{"class":108}," core.sync_directory(tmp_path, ",[91,964,410],{"class":135},[91,966,139],{"class":104},[91,968,969],{"class":108},"bucket)\n",[91,971,972],{"class":93,"line":177},[91,973,122],{"emptyLinePlaceholder":121},[91,975,976,979,982,985,988,991,993,996,998,1001,1003,1006],{"class":93,"line":183},[91,977,978],{"class":104},"    assert",[91,980,981],{"class":108}," result ",[91,983,984],{"class":104},"==",[91,986,987],{"class":108}," SyncResult(",[91,989,990],{"class":135},"uploaded",[91,992,139],{"class":104},[91,994,995],{"class":142},"0",[91,997,146],{"class":108},[91,999,1000],{"class":135},"skipped",[91,1002,139],{"class":104},[91,1004,1005],{"class":142},"1",[91,1007,156],{"class":108},[82,1009,1011],{"className":84,"code":1010,"language":86,"meta":87,"style":87},"def test_command_uses_the_injected_services(cli):\n    services = Services(settings=Settings(), bucket=FakeBucket(), clock=lambda: FIXED_TIME)\n\n    result = cli.invoke(app, [\"sync\", \"data\"], obj=services)     # runner passes ctx.obj\n\n    assert result.exit_code == 0\n    assert services.bucket.uploaded == [\"data\u002Fa.txt\"]\n",[38,1012,1013,1023,1059,1063,1094,1098,1110],{"__ignoreMap":87},[91,1014,1015,1017,1020],{"class":93,"line":94},[91,1016,197],{"class":104},[91,1018,1019],{"class":128}," test_command_uses_the_injected_services",[91,1021,1022],{"class":108},"(cli):\n",[91,1024,1025,1027,1029,1032,1035,1037,1040,1042,1044,1047,1050,1052,1054,1057],{"class":93,"line":101},[91,1026,392],{"class":108},[91,1028,139],{"class":104},[91,1030,1031],{"class":108}," Services(",[91,1033,1034],{"class":135},"settings",[91,1036,139],{"class":104},[91,1038,1039],{"class":108},"Settings(), ",[91,1041,410],{"class":135},[91,1043,139],{"class":104},[91,1045,1046],{"class":108},"FakeBucket(), ",[91,1048,1049],{"class":135},"clock",[91,1051,259],{"class":104},[91,1053,640],{"class":108},[91,1055,1056],{"class":142},"FIXED_TIME",[91,1058,156],{"class":108},[91,1060,1061],{"class":93,"line":118},[91,1062,122],{"emptyLinePlaceholder":121},[91,1064,1065,1067,1069,1072,1075,1077,1080,1083,1086,1088,1091],{"class":93,"line":125},[91,1066,402],{"class":108},[91,1068,139],{"class":104},[91,1070,1071],{"class":108}," cli.invoke(app, [",[91,1073,1074],{"class":434},"\"sync\"",[91,1076,146],{"class":108},[91,1078,1079],{"class":434},"\"data\"",[91,1081,1082],{"class":108},"], ",[91,1084,1085],{"class":135},"obj",[91,1087,139],{"class":104},[91,1089,1090],{"class":108},"services)     ",[91,1092,1093],{"class":97},"# runner passes ctx.obj\n",[91,1095,1096],{"class":93,"line":159},[91,1097,122],{"emptyLinePlaceholder":121},[91,1099,1100,1102,1105,1107],{"class":93,"line":171},[91,1101,978],{"class":104},[91,1103,1104],{"class":108}," result.exit_code ",[91,1106,984],{"class":104},[91,1108,1109],{"class":142}," 0\n",[91,1111,1112,1114,1117,1119,1122,1125],{"class":93,"line":177},[91,1113,978],{"class":104},[91,1115,1116],{"class":108}," services.bucket.uploaded ",[91,1118,984],{"class":104},[91,1120,1121],{"class":108}," [",[91,1123,1124],{"class":434},"\"data\u002Fa.txt\"",[91,1126,1127],{"class":108},"]\n",[10,1129,1130,1133,1134,1137,1138,1141],{},[38,1131,1132],{},"CliRunner.invoke"," accepts an ",[38,1135,1136],{},"obj="," argument that becomes ",[38,1139,1140],{},"ctx.obj",", which means a command test can\nsupply the whole service graph without touching the callback. That single capability is what makes\nthe context-object pattern comfortable to test.",[14,1143,1145],{"id":1144},"retrofitting-this-into-existing-code","Retrofitting this into existing code",[10,1147,1148],{},"Most codebases arrive at this pattern from the opposite direction: a module-level client that grew\nbecause it was the obvious place to put it. The refactor is safe if you do it in three steps.",[10,1150,1151,1154],{},[26,1152,1153],{},"Step one: add the parameter, keep the global."," Give the function an optional parameter that\nfalls back to the existing global. Nothing calling it needs to change, and tests can start passing\na fake immediately.",[82,1156,1158],{"className":84,"code":1157,"language":86,"meta":87,"style":87},"_client = S3Bucket()          # the existing global, untouched for now\n\ndef sync_directory(source: Path, *, bucket: BucketClient | None = None) -> SyncResult:\n    bucket = bucket or _client\n    ...\n",[38,1159,1160,1173,1177,1201,1214],{"__ignoreMap":87},[91,1161,1162,1165,1167,1170],{"class":93,"line":94},[91,1163,1164],{"class":108},"_client ",[91,1166,139],{"class":104},[91,1168,1169],{"class":108}," S3Bucket()          ",[91,1171,1172],{"class":97},"# the existing global, untouched for now\n",[91,1174,1175],{"class":93,"line":101},[91,1176,122],{"emptyLinePlaceholder":121},[91,1178,1179,1181,1183,1186,1188,1191,1193,1195,1197,1199],{"class":93,"line":118},[91,1180,197],{"class":104},[91,1182,492],{"class":128},[91,1184,1185],{"class":108},"(source: Path, ",[91,1187,656],{"class":104},[91,1189,1190],{"class":108},", bucket: BucketClient ",[91,1192,305],{"class":104},[91,1194,308],{"class":142},[91,1196,311],{"class":104},[91,1198,308],{"class":142},[91,1200,541],{"class":108},[91,1202,1203,1205,1207,1209,1211],{"class":93,"line":125},[91,1204,546],{"class":108},[91,1206,139],{"class":104},[91,1208,551],{"class":108},[91,1210,554],{"class":104},[91,1212,1213],{"class":108}," _client\n",[91,1215,1216],{"class":93,"line":159},[91,1217,562],{"class":142},[10,1219,1220,1223],{},[26,1221,1222],{},"Step two: push construction upwards."," Build the client in the callback, put it on the context,\nand pass it from each command. The global is now unused by anything except the fallback.",[10,1225,1226,1229,1230,1232],{},[26,1227,1228],{},"Step three: delete the global."," Make the parameter required, or keep the ",[38,1231,319],{}," default and\nconstruct inside — but with nothing at module level. The import-time side effect disappears, which\nalso removes it from your start-up cost.",[10,1234,1235],{},"Each step is a separate commit, the tests pass throughout, and at no point does the codebase have\ntwo competing sources for the same object.",[10,1237,1238],{},"The one thing to resist is doing all three at once across a dozen call sites. Half-finished\ninjection — some callers passing, some relying on a global — is harder to reason about than either\nend state.",[14,1240,1242],{"id":1241},"conclusion","Conclusion",[10,1244,1245],{},"Build collaborators once at the boundary, hand them down explicitly, and describe the seam with a\nprotocol. Two habits, no framework, and the result is a codebase where tests construct what they\nneed instead of patching what they cannot reach.",[14,1247,1249],{"id":1248},"frequently-asked-questions","Frequently asked questions",[1251,1252,1254],"h3",{"id":1253},"is-a-dependency-injection-library-worth-it","Is a dependency injection library worth it?",[10,1256,1257,1258,1261],{},"Rarely for a CLI. Libraries like ",[38,1259,1260],{},"dependency-injector"," solve wiring problems that appear in\nlong-lived applications with many interdependent services and lifecycles. A command-line tool\nconstructs a handful of objects once and exits; a frozen dataclass does the same job with no\nindirection to learn.",[1251,1263,1265],{"id":1264},"how-do-i-inject-into-a-command-that-click-constructs","How do I inject into a command that Click constructs?",[10,1267,1268,1269,1271,1272,1274],{},"Through the context, which is exactly what it exists for. The callback assigns ",[38,1270,1140],{},", commands\nread it, and the test runner can supply it directly with ",[38,1273,1136],{},". There is no need for the framework\nto know about your objects.",[1251,1276,1278],{"id":1277},"what-about-expensive-collaborators-only-one-command-needs","What about expensive collaborators only one command needs?",[10,1280,1281,1282,1284,1285,1287],{},"Build them lazily. Either give the ",[38,1283,460],{}," object a cached property, or have the command\nconstruct that one collaborator itself from settings. Constructing a data-warehouse client in the\ncallback so that ",[38,1286,871],{}," pays for it is a common and avoidable mistake.",[1251,1289,1291],{"id":1290},"does-this-conflict-with-lazy-command-loading","Does this conflict with lazy command loading?",[10,1293,1294],{},"No — they compose. The registry imports a command module on demand, and that module's function\nstill receives services from the context. What you should avoid is constructing collaborators at\nmodule import time, which would defeat both patterns at once.",[1251,1296,1298],{"id":1297},"how-do-i-handle-a-dependency-needed-by-only-some-commands-in-a-group","How do I handle a dependency needed by only some commands in a group?",[10,1300,1301,1302,1305,1306,1309,1310,1313],{},"Put it on the group's own callback rather than the root. A ",[38,1303,1304],{},"db"," sub-app can build a connection in\nits callback, so ",[38,1307,1308],{},"mytool sync"," never opens one, and ",[38,1311,1312],{},"mytool db migrate"," still gets it through the\ncontext chain.",[14,1315,1317],{"id":1316},"related","Related",[19,1319,1320,1326,1333,1339,1346],{},[22,1321,1322,1323],{},"Up: ",[65,1324,1325],{"href":67},"Structuring multi-command Python CLIs",[22,1327,1328,1329],{},"Sideways: ",[65,1330,1332],{"href":1331},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-state-with-click-context-objects\u002F","Sharing state with Click context objects",[22,1334,1328,1335],{},[65,1336,1338],{"href":1337},"\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",[22,1340,1341,1342],{},"Related: ",[65,1343,1345],{"href":1344},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fmocking-filesystem-and-network-in-cli-tests\u002F","Mocking the filesystem and network in CLI tests",[22,1347,1341,1348],{},[65,1349,1351],{"href":1350},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002F","Testing Python CLI applications",[1353,1354,1355],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}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 .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}",{"title":87,"searchDepth":101,"depth":101,"links":1357},[1358,1359,1360,1361,1362,1363,1364,1365,1366,1367,1368,1375],{"id":16,"depth":101,"text":17},{"id":59,"depth":101,"text":60},{"id":72,"depth":101,"text":73},{"id":464,"depth":101,"text":465},{"id":580,"depth":101,"text":581},{"id":834,"depth":101,"text":835},{"id":854,"depth":101,"text":855},{"id":885,"depth":101,"text":886},{"id":1144,"depth":101,"text":1145},{"id":1241,"depth":101,"text":1242},{"id":1248,"depth":101,"text":1249,"children":1369},[1370,1371,1372,1373,1374],{"id":1253,"depth":118,"text":1254},{"id":1264,"depth":118,"text":1265},{"id":1277,"depth":118,"text":1278},{"id":1290,"depth":118,"text":1291},{"id":1297,"depth":118,"text":1298},{"id":1316,"depth":101,"text":1317},"2026-08-01","Wire collaborators into Python CLI commands without globals - default parameters, context objects, protocols, and tests that need no monkeypatching.","advanced",false,"md",{},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fdependency-injection-patterns-for-cli-commands",{"title":5,"description":1377},"modern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fdependency-injection-patterns-for-cli-commands\u002Findex",[1386,1387,1388,1389,1390],"architecture","dependency-injection","testing","click","typer","YeCvRgBOov3SttXpNRolMU2WHz9VEBdw-TSXNBwiY2c",[1393,1396,1399,1402,1405,1408,1411,1414,1417,1420,1423,1426,1429,1432,1435,1438,1441,1444,1447,1450,1453,1456,1459,1462,1465,1468,1471,1474,1477,1480,1483,1486,1489,1492,1495,1498,1501,1504,1507,1510,1513,1516,1519,1522,1525,1528,1531,1534,1537,1540,1543,1546,1549,1552,1555,1558,1561,1564,1567,1570,1573,1576,1579,1582,1585,1588,1591,1594,1597,1600,1603,1606,1609,1612,1615,1618,1621,1624,1627,1630,1633,1636,1639,1642,1645,1648,1651,1654,1657,1660,1663,1666,1669,1672,1675,1678,1681,1684,1687,1690,1693,1696,1699,1702,1705,1708,1711,1714,1717,1720,1723,1726,1729,1732,1735,1738,1741,1744,1747,1750,1753,1756,1759,1762,1765,1768,1771,1774,1777,1780,1783,1786,1789,1792,1795,1798,1801,1804,1807,1810,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,1921,1924,1927,1930,1933,1936,1939,1942,1945,1948,1951,1954,1957,1960,1963,1966,1969,1972,1975,1978,1981,1984,1987,1990,1993,1996,1999,2002,2005,2008,2011,2014,2017,2020,2023,2026,2029,2032,2035,2038,2041,2044,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],{"path":1394,"title":1395},"\u002Fabout","About Python CLI Toolcraft",{"path":1397,"title":1398},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies","Advanced Argument Validation Strategies",{"path":1400,"title":1401},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fparsing-nested-json-arguments-in-python-clis","Parsing Nested JSON Args in Python CLIs",{"path":1403,"title":1404},"\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":1406,"title":1407},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-dependent-and-conflicting-options","Validating Dependent and Conflicting CLI Options",{"path":1409,"title":1410},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-file-and-directory-paths-in-clis","Validating File and Directory Paths in CLIs",{"path":1412,"title":1413},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-urls-hosts-and-ports","Validating URLs, Hosts and Ports in Python CLI Arguments",{"path":1415,"title":1416},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fwriting-custom-click-parameter-types","Writing Custom Click Parameter Types",{"path":1418,"title":1419},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fbrowsing-records-with-a-textual-datatable","Browsing Records with a Textual DataTable Picker",{"path":1421,"title":1422},"\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":1424,"title":1425},"\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":1427,"title":1428},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual","Building Terminal UIs with Textual for Python CLIs",{"path":1430,"title":1431},"\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":1433,"title":1434},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fstyling-textual-apps-with-tcss","Styling Textual Apps with TCSS",{"path":1436,"title":1437},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Ftesting-textual-apps-with-pilot","Testing Textual Apps with Pilot",{"path":1439,"title":1440},"\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":1442,"title":1443},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fdocumenting-environment-variables-in-help","Documenting Environment Variables in CLI Help",{"path":1445,"title":1446},"\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":1448,"title":1449},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation","CLI Help Output and Documentation",{"path":1451,"title":1452},"\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":1454,"title":1455},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fversioning-and-deprecating-cli-flags","Versioning and Deprecating CLI Flags",{"path":1457,"title":1458},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fwriting-help-text-users-actually-read","Writing Help Text Users Actually Read",{"path":1460,"title":1461},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fadapting-output-to-terminal-width","Adapting Python CLI Output to Terminal Width",{"path":1463,"title":1464},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fdetecting-ci-environments-and-non-interactive-shells","Detecting CI Environments and Non-Interactive Shells",{"path":1466,"title":1467},"\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":1469,"title":1470},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fhandling-ansi-escape-codes-on-windows-consoles","Handling ANSI Escape Codes on Windows Consoles",{"path":1472,"title":1473},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility","Cross-Platform Terminal Compatibility for Python CLIs",{"path":1475,"title":1476},"\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":1478,"title":1479},"\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":1481,"title":1482},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fchoosing-exit-codes-for-cli-tools","Choosing Exit Codes for CLI Tools",{"path":1484,"title":1485},"\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":1487,"title":1488},"\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":1490,"title":1491},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Ffriendly-error-messages-and-tracebacks","Friendly Error Messages and Tracebacks",{"path":1493,"title":1494},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fhandling-keyboard-interrupt-cleanly","Handling Keyboard Interrupt Cleanly",{"path":1496,"title":1497},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes","Error Handling and Exit Codes for CLIs",{"path":1499,"title":1500},"\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":1502,"title":1503},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fwriting-crash-reports-users-can-send","Writing Crash Reports Users Can Send",{"path":1505,"title":1506},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Fconfig-precedence-flags-env-files-defaults","Config Precedence: Flags, Env, Files, Defaults",{"path":1508,"title":1509},"\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":1511,"title":1512},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars","Handling Config Files and Env Vars in CLIs",{"path":1514,"title":1515},"\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":1517,"title":1518},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Freading-toml-config-with-tomllib","Reading TOML Config with tomllib in Python CLIs",{"path":1520,"title":1521},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Ftyped-settings-with-pydantic-settings","Typed Settings with pydantic-settings in Python CLIs",{"path":1523,"title":1524},"\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":1526,"title":1527},"\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":1529,"title":1530},"\u002Fadvanced-input-parsing-user-experience","Advanced Input Parsing for Python CLIs",{"path":1532,"title":1533},"\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":1535,"title":1536},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Fbuilding-interactive-prompts-and-menus","Building Interactive Prompts and Menus in Python CLIs",{"path":1538,"title":1539},"\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":1541,"title":1542},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich","Interactive Terminal UI with Rich",{"path":1544,"title":1545},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Flive-dashboards-with-rich-live","Live Dashboards with Rich Live in Python CLIs",{"path":1547,"title":1548},"\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":1550,"title":1551},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Frendering-tables-and-json-with-rich","Rendering Tables and JSON with Rich",{"path":1553,"title":1554},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Ftheming-rich-output-consistently","Theming Rich Output Consistently in Python CLIs",{"path":1556,"title":1557},"\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":1559,"title":1560},"\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":1562,"title":1563},"\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":1565,"title":1566},"\u002Fadvanced-input-parsing-user-experience\u002Foutput-formats-for-data-clis","Output Formats for Data-Heavy Python CLIs",{"path":1568,"title":1569},"\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":1571,"title":1572},"\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":1574,"title":1575},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fargcomplete-for-argparse-clis","Tab Completion for argparse CLIs with argcomplete",{"path":1577,"title":1578},"\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":1580,"title":1581},"\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":1583,"title":1584},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis","Shell Completion for Python CLIs",{"path":1586,"title":1587},"\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":1589,"title":1590},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fshipping-completion-scripts-with-packages","Shipping Shell Completion Scripts with a Python CLI",{"path":1592,"title":1593},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Ftesting-shell-completion-in-python-clis","Testing Shell Completion in Python CLIs",{"path":1595,"title":1596},"\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":1598,"title":1599},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fadding-verbose-and-quiet-logging-flags","Adding Verbose and Quiet Logging Flags",{"path":1601,"title":1602},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps","Structured Logging for CLI Apps",{"path":1604,"title":1605},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Flogging-with-structlog-in-a-cli","Logging with structlog in a Python CLI",{"path":1607,"title":1608},"\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":1610,"title":1611},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fstructured-json-logging-in-python-clis","Structured JSON Logging in Python CLIs",{"path":1613,"title":1614},"\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":1616,"title":1617},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fdetecting-tty-and-adapting-output","Detecting a TTY and Adapting Output",{"path":1619,"title":1620},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Femitting-json-output-for-scripting","Emitting JSON Output for Scripting",{"path":1622,"title":1623},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fhandling-broken-pipe-and-sigpipe","Handling Broken Pipe and SIGPIPE",{"path":1625,"title":1626},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes","Working with stdin, stdout and Pipes",{"path":1628,"title":1629},"\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":1631,"title":1632},"\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":1634,"title":1635},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Freading-piped-input-in-python-clis","Reading Piped Input in Python CLIs",{"path":1637,"title":1638},"\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":1640,"title":1641},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fdownloading-files-with-progress-in-python","Downloading Files with Progress in Python CLIs",{"path":1643,"title":1644},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis","Calling HTTP APIs from Python CLIs",{"path":1646,"title":1647},"\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":1649,"title":1650},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Foauth-device-flow-login-for-clis","OAuth Device Flow Login for Python CLIs",{"path":1652,"title":1653},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fpaginating-api-results-in-a-cli","Paginating API Results in a Python CLI",{"path":1655,"title":1656},"\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":1658,"title":1659},"\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":1661,"title":1662},"\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":1664,"title":1665},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis","Concurrency and Async in Python CLIs",{"path":1667,"title":1668},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fmultiprocessing-for-cpu-bound-cli-tasks","Multiprocessing for CPU-Bound CLI Tasks",{"path":1670,"title":1671},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fparallelising-cli-work-with-thread-pools","Parallelising CLI Work with Thread Pools",{"path":1673,"title":1674},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Frate-limiting-concurrent-requests-in-clis","Rate-Limiting Concurrent Requests in Python CLIs",{"path":1676,"title":1677},"\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":1679,"title":1680},"\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":1682,"title":1683},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fstructured-concurrency-with-taskgroups-in-clis","Structured Concurrency with TaskGroups in Python CLIs",{"path":1685,"title":1686},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fcross-platform-paths-with-pathlib","Cross-Platform Paths with pathlib in CLIs",{"path":1688,"title":1689},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Ffile-locking-for-concurrent-cli-runs","File Locking for Concurrent CLI Runs in Python",{"path":1691,"title":1692},"\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":1694,"title":1695},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes","Filesystem Paths and Atomic Writes for CLIs",{"path":1697,"title":1698},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fsafe-temporary-files-and-directories","Safe Temporary Files and Directories in CLIs",{"path":1700,"title":1701},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fstoring-app-data-with-platformdirs","Storing CLI App Data with platformdirs",{"path":1703,"title":1704},"\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":1706,"title":1707},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fwriting-files-atomically-in-python-clis","Writing Files Atomically in Python CLIs",{"path":1709,"title":1710},"\u002Fcli-runtime-systems-integration","CLI Runtime & Systems Integration for Python",{"path":1712,"title":1713},"\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":1715,"title":1716},"\u002Fcli-runtime-systems-integration\u002Flocal-state-and-sqlite-in-python-clis","Local State and SQLite in Python CLIs",{"path":1718,"title":1719},"\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":1721,"title":1722},"\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":1724,"title":1725},"\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":1727,"title":1728},"\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":1730,"title":1731},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fhandling-sigterm-and-graceful-shutdown","Handling SIGTERM and Graceful Shutdown in CLIs",{"path":1733,"title":1734},"\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":1736,"title":1737},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis","Long-Running and Watch-Mode Python CLIs",{"path":1739,"title":1740},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Freloading-config-on-sighup","Reloading Configuration on SIGHUP in a Python CLI",{"path":1742,"title":1743},"\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":1745,"title":1746},"\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":1748,"title":1749},"\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":1751,"title":1752},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Favoiding-shell-injection-in-python-clis","Avoiding Shell Injection in Python CLIs",{"path":1754,"title":1755},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fcalling-external-commands-safely-with-subprocess","Calling External Commands Safely with subprocess",{"path":1757,"title":1758},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fhandling-subprocess-timeouts-and-exit-codes","Handling Subprocess Timeouts and Exit Codes",{"path":1760,"title":1761},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis","Running Subprocesses from Python CLIs",{"path":1763,"title":1764},"\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":1766,"title":1767},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fpiping-between-subprocesses-in-python","Piping Between Subprocesses in Python Without a Shell",{"path":1769,"title":1770},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fstreaming-subprocess-output-in-real-time","Streaming Subprocess Output in Real Time",{"path":1772,"title":1773},"\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":1775,"title":1776},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis","Secrets and Credentials in Python CLIs",{"path":1778,"title":1779},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fprompting-for-passwords-securely","Prompting for Passwords Securely in Python CLIs",{"path":1781,"title":1782},"\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":1784,"title":1785},"\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":1787,"title":1788},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Frefreshing-expired-tokens-automatically","Refreshing Expired Tokens Automatically in a Python CLI",{"path":1790,"title":1791},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fstoring-tokens-with-keyring","Storing CLI Tokens Securely with keyring",{"path":1793,"title":1794},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fsupporting-multiple-profiles-and-accounts","Supporting Multiple Profiles and Accounts in CLIs",{"path":1796,"title":1797},"\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":1799,"title":1800},"\u002Fcli-runtime-systems-integration\u002Fupdate-checks-and-self-updating-clis","Update Checks, Upgrade Commands and Telemetry for Python CLIs",{"path":1802,"title":1803},"\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":1805,"title":1806},"\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":1808,"title":1809},"\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":912,"title":1811},"Python CLI Toolcraft",{"path":1813,"title":1814},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cleo","Building a Python CLI with Cleo Command Classes",{"path":1816,"title":1817},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cyclopts","Building a Type-Hinted Python CLI with Cyclopts",{"path":1819,"title":1820},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks","Beyond Click and Typer: Alternative Python CLI Frameworks",{"path":1822,"title":1823},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fquick-clis-from-functions-with-python-fire","Quick CLIs from Functions with Python Fire",{"path":1825,"title":1826},"\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":1828,"title":1829},"\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":1831,"title":1832},"\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":1834,"title":1835},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fguarding-startup-with-import-tests","Guarding CLI Startup with Import Tests",{"path":1837,"title":1838},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading","CLI Startup Performance and Lazy Loading",{"path":1840,"title":1841},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Flazy-loading-subcommands-for-faster-startup","Lazy Loading Subcommands for Faster Startup",{"path":1843,"title":1844},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fprofiling-python-cli-startup-time","Profiling Python CLI Startup Time",{"path":1846,"title":1847},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Freducing-cli-dependency-weight","Reducing CLI Dependency Weight",{"path":1849,"title":1850},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-subparsers-for-subcommands","argparse Subparsers for Subcommands",{"path":1852,"title":1853},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-vs-click-vs-typer-comparison","argparse vs Click vs Typer Compared",{"path":1855,"title":1856},"\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":1858,"title":1859},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse","Command-Line Parsing with argparse",{"path":1861,"title":1862},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmigrating-from-argparse-to-typer","Migrating from argparse to Typer",{"path":1864,"title":1865},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmutually-exclusive-options-in-argparse","Mutually Exclusive Options in argparse",{"path":1867,"title":1868},"\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":1870,"title":1871},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fwriting-custom-argparse-actions","Writing Custom argparse Actions in Python",{"path":1873,"title":1874},"\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":1876,"title":1877},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fdesigning-idempotent-commands","Designing Idempotent Commands in a Python CLI",{"path":1879,"title":1880},"\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":1882,"title":1883},"\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":1885,"title":1886},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions","Designing CLI Interfaces and Conventions in Python",{"path":1888,"title":1889},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fnaming-commands-and-flags-consistently","Naming Commands and Flags Consistently in Python CLIs",{"path":1891,"title":1892},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fpositional-arguments-vs-options","Positional Arguments vs Options: Designing a CLI Signature",{"path":1894,"title":1895},"\u002Fmodern-python-cli-frameworks-architecture","Python CLI Frameworks and Architecture",{"path":1897,"title":1898},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fdiscovering-plugins-with-entry-points","Discovering Plugins with Entry Points in Python CLIs",{"path":1900,"title":1901},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fhook-based-plugins-with-pluggy","Hook-Based Plugins for Python CLIs with pluggy",{"path":1903,"title":1904},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis","Plugin Architectures for Extensible CLIs",{"path":1906,"title":1907},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fisolating-plugin-failures","Isolating Plugin Failures in an Extensible Python CLI",{"path":1909,"title":1910},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Ftesting-plugins-against-the-host-cli","Testing Plugins Against the Host CLI",{"path":1912,"title":1913},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fversioning-a-plugin-api","Versioning a Plugin API for a Python CLI",{"path":1915,"title":1916},"\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":1918,"title":1919},"\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":1382,"title":5},{"path":1922,"title":1923},"\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":1925,"title":1926},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis","Structuring Multi-Command Python CLIs",{"path":1928,"title":1929},"\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":1931,"title":1932},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fregistering-commands-from-modules-automatically","Registering CLI Commands from Modules Automatically",{"path":1934,"title":1935},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-common-options-across-commands","Sharing Common Options Across Python CLI Commands",{"path":1937,"title":1938},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-state-with-click-context-objects","Sharing State with Click Context Objects",{"path":1940,"title":1941},"\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":1943,"title":1944},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications","Testing Python CLI Applications",{"path":1946,"title":1947},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fmeasuring-cli-test-coverage","Measuring CLI Test Coverage",{"path":1949,"title":1950},"\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":1952,"title":1953},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fproperty-based-testing-cli-arguments-with-hypothesis","Property-Based Testing CLI Arguments with Hypothesis",{"path":1955,"title":1956},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fsnapshot-testing-cli-output","Snapshot Testing CLI Output",{"path":1958,"title":1959},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-click-commands-with-clirunner","Testing Click Commands with CliRunner",{"path":1961,"title":1962},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-commands-that-call-subprocesses","Testing Python CLI Commands That Call Subprocesses",{"path":1964,"title":1965},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-interactive-prompts-and-stdin","Testing Interactive Prompts and stdin",{"path":1967,"title":1968},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftranscript-tests-for-cli-commands","Transcript Tests for Python CLI Commands",{"path":1970,"title":1971},"\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":1973,"title":1974},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fbuilding-dynamic-commands-in-click","Building Dynamic Commands in Click",{"path":1976,"title":1977},"\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":1979,"title":1980},"\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":1982,"title":1983},"\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":1985,"title":1986},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each","Typer vs Click: When to Use Each",{"path":1988,"title":1989},"\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":1991,"title":1992},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Ftyper-callback-functions-explained","Typer callback functions explained",{"path":1994,"title":1995},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fusing-annotated-options-in-typer","Using Annotated Options in Typer",{"path":1997,"title":1998},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fautomating-releases-from-git-tags","Automating Python CLI Releases from Git Tags",{"path":2000,"title":2001},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fcaching-uv-dependencies-in-ci","Caching uv Dependencies in CI for Python CLIs",{"path":2003,"title":2004},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis","CI\u002FCD Pipelines for Python CLIs",{"path":2006,"title":2007},"\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":2009,"title":2010},"\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":2012,"title":2013},"\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":2015,"title":2016},"\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":2018,"title":2019},"\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":2021,"title":2022},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fbuilding-a-cookiecutter-template-for-typer-clis","Building a Cookiecutter Template for Typer CLIs",{"path":2024,"title":2025},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fcopier-vs-cookiecutter-for-cli-templates","Copier vs Cookiecutter for CLI Templates",{"path":2027,"title":2028},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter","CLI Project Scaffolding with Cookiecutter",{"path":2030,"title":2031},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fpost-generation-hooks-in-cli-templates","Post-Generation Hooks in Python CLI Templates",{"path":2033,"title":2034},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftemplate-variables-and-conditional-files","Template Variables and Conditional Files in CLI Templates",{"path":2036,"title":2037},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftesting-a-project-template-with-pytest","Testing a CLI Project Template with pytest",{"path":2039,"title":2040},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fupdating-generated-projects-with-copier-update","Updating Generated CLI Projects with copier update",{"path":2042,"title":2043},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbuilding-cross-platform-release-binaries-in-ci","Building Cross-Platform Release Binaries in CI",{"path":2045,"title":2046},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbundling-a-python-cli-with-pyinstaller","Bundling a Python CLI with PyInstaller",{"path":2048,"title":2049},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fcode-signing-and-notarizing-cli-binaries","Code Signing and Notarizing Python CLI Binaries",{"path":2051,"title":2052},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fhomebrew-and-scoop-packaging-for-python-clis","Homebrew and Scoop Packaging for Python CLIs",{"path":2054,"title":2055},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries","Distributing CLIs as Standalone Binaries",{"path":2057,"title":2058},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fnuitka-vs-pyinstaller-for-python-clis","Nuitka vs PyInstaller for Python CLI Binaries",{"path":2060,"title":2061},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Freducing-pyinstaller-binary-size","Reducing the Size of a PyInstaller CLI Binary",{"path":2063,"title":2064},"\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":2066,"title":2067},"\u002Fproject-setup-dependency-management","Project Setup & Dependency Management",{"path":2069,"title":2070},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fconfiguring-ruff-for-a-cli-project","Configuring Ruff for a Python CLI Project",{"path":2072,"title":2073},"\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":2075,"title":2076},"\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":2078,"title":2079},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code","Linting and Type-Checking Python CLI Code",{"path":2081,"title":2082},"\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":2084,"title":2085},"\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":2087,"title":2088},"\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":2090,"title":2091},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fautomating-changelogs-with-conventional-commits","Automating Changelogs with Conventional Commits",{"path":2093,"title":2094},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fbumping-versions-consistently-across-a-cli-project","Bumping Versions Consistently Across a Python CLI Project",{"path":2096,"title":2097},"\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":2099,"title":2100},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fexposing-version-info-and-build-metadata","Exposing Version Info and Build Metadata",{"path":2102,"title":2103},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs","Managing CLI Versioning & Changelogs",{"path":2105,"title":2106},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fsemantic-versioning-policy-for-cli-tools","A Semantic Versioning Policy for CLI Tools",{"path":2108,"title":2109},"\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":2111,"title":2112},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbuilding-wheels-and-sdists-for-python-clis","Building Wheels and sdists for Python CLIs",{"path":2114,"title":2115},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbundling-data-files-with-importlib-resources","Bundling Data Files with importlib.resources in CLIs",{"path":2117,"title":2118},"\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":2120,"title":2121},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution","Packaging Python CLIs for Distribution",{"path":2123,"title":2124},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Finstalling-and-distributing-clis-with-pipx","Installing and Distributing CLIs with pipx",{"path":2126,"title":2127},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Foptional-dependencies-and-extras-for-clis","Optional Dependencies and Extras for Python CLIs",{"path":2129,"title":2130},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fpublishing-a-python-cli-to-pypi","Publishing a Python CLI to PyPI",{"path":2132,"title":2133},"\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":2135,"title":2136},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fdynamic-versioning-with-poetry-plugins","Dynamic Versioning for a Poetry CLI from Git Tags",{"path":2138,"title":2139},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development","Poetry Workflows for CLI Development",{"path":2141,"title":2142},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fmanaging-poetry-lock-files-for-cli-tools","Managing Poetry Lock Files for CLI Tools",{"path":2144,"title":2145},"\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":2147,"title":2148},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-dependency-groups-for-cli-tooling","Poetry Dependency Groups for CLI Tooling",{"path":2150,"title":2151},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-entry-points-and-scripts-for-clis","Poetry Entry Points and Scripts for CLIs",{"path":2153,"title":2154},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpublishing-a-cli-with-poetry","Building and Publishing a Python CLI with Poetry",{"path":2156,"title":2157},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects","Pre-commit Hooks for CLI Projects",{"path":2159,"title":2160},"\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":2162,"title":2163},"\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":2165,"title":2166},"\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":2168,"title":2169},"\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":2171,"title":2172},"\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":2174,"title":2175},"\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":2177,"title":2178},"\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":2180,"title":2181},"\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":2183,"title":2184},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain","Securing the Supply Chain of a Python CLI",{"path":2186,"title":2187},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpinning-dependencies-with-hashes","Pinning a Python CLI’s Dependencies with Hashes",{"path":2189,"title":2190},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpublishing-attestations-and-verifying-releases","Publishing Attestations and Verifying Python CLI Releases",{"path":2192,"title":2193},"\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":2195,"title":2196},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management","uv for Python CLI Dependency Management",{"path":2198,"title":2199},"\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":2201,"title":2202},"\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":2204,"title":2205},"\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":2207,"title":2208},"\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":2210,"title":2211},"\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":2213,"title":2214},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis","uv Workspaces for Multi-Package Python CLIs",{"path":2216,"title":2217},"\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":2219,"title":2220},"\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":2222,"title":2223},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices","Python CLI Env Isolation Best Practices",{"path":2225,"title":2226},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fisolating-cli-tools-from-project-dependencies","Isolating CLI Tools from Your Project’s Dependencies",{"path":2228,"title":2229},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fmanaging-virtual-environments-for-cross-platform-clis","Managing Python CLI Virtual Environments",{"path":2231,"title":2232},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fpinning-the-python-version-for-a-cli","Pinning the Python Version for a CLI",{"path":2234,"title":2235},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fsupporting-multiple-python-versions-with-nox","Supporting Multiple Python Versions with nox",1790967541380]