[{"data":1,"prerenderedAt":1816},["ShallowReactive",2],{"page-\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fenforcing-import-boundaries-in-a-cli-codebase\u002F":3,"content-directory":1268},{"id":4,"title":5,"body":6,"date":1254,"description":1255,"difficulty":1256,"draft":1257,"extension":1258,"meta":1259,"navigation":197,"path":1260,"seo":1261,"stem":1262,"tags":1263,"updated":1254,"__hash__":1267},"content\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fenforcing-import-boundaries-in-a-cli-codebase\u002Findex.md","Enforcing Import Boundaries in a Python CLI Codebase",{"type":7,"value":8,"toc":1233},"minimark",[9,36,41,71,75,78,82,110,116,120,133,489,500,503,508,522,540,550,570,574,577,592,596,602,867,877,881,884,995,1007,1011,1014,1047,1051,1054,1096,1107,1111,1117,1121,1125,1136,1140,1157,1161,1169,1173,1187,1191,1194,1198,1229],[10,11,12,13,17,18,21,22,25,26,29,30,35],"p",{},"Every guide to structuring a CLI recommends the same shape: a thin command layer on top, services in the middle, and core logic at the bottom that knows nothing about Typer, Rich or HTTP. The shape pays off — core logic is reusable from other programs, testable without a CLI runner, and fast to import — until someone adds ",[14,15,16],"code",{},"from rich import print"," to a core module to debug something, or imports ",[14,19,20],{},"typer.BadParameter"," into a validator because it gives a nicer error. Each shortcut is small; together they turn the layers back into a tangle, and nobody notices until ",[14,23,24],{},"mytool --help"," takes 400 ms or the core package cannot be imported without the whole CLI. This guide turns the architecture into rules a machine checks, using ",[14,27,28],{},"import-linter",", with contracts for layers, forbidden dependencies and independent commands, plus a startup-time guard. It is part of the ",[31,32,34],"a",{"href":33},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002F","linting and type-checking topic",".",[37,38,40],"h2",{"id":39},"prerequisites","Prerequisites",[42,43,44,63],"ul",{},[45,46,47,48,51,52,51,55,58,59,35],"li",{},"A CLI package with some layered structure — for example ",[14,49,50],{},"mytool.cli",", ",[14,53,54],{},"mytool.services",[14,56,57],{},"mytool.core"," — as described in ",[31,60,62],{"href":61},"\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",[45,64,65,67,68,35],{},[14,66,28],{}," as a dev dependency: ",[14,69,70],{},"uv add --dev import-linter",[37,72,74],{"id":73},"the-layers-worth-protecting","The layers worth protecting",[10,76,77],{},"A typical CLI has three layers, and the rule is that imports point downward only:",[79,80],"inline-diagram",{"name":81},"lint-layer-contract",[42,83,84,92,103],{},[45,85,86,91],{},[87,88,89],"strong",{},[14,90,50],{}," holds the Typer or Click app, command functions and output formatting. It may import anything.",[45,93,94,98,99,102],{},[87,95,96],{},[14,97,54],{}," orchestrates: API clients, the git wrapper, file storage, credential lookup. It may import ",[14,100,101],{},"core",", and the libraries it wraps, but not the CLI framework.",[45,104,105,109],{},[87,106,107],{},[14,108,57],{}," holds domain logic and data models — pure Python that takes values and returns values. It imports nothing from the layers above and no heavy third-party libraries.",[10,111,112,113,115],{},"When ",[14,114,101],{}," stays pure, it can be imported by a web service, a notebook or a test without dragging in a terminal UI; it can be unit-tested without mocks; and importing it costs almost nothing at startup, which matters because every command imports it.",[37,117,119],{"id":118},"the-recipe-import-linter-contracts","The recipe: import-linter contracts",[10,121,122,124,125,128,129,132],{},[14,123,28],{}," builds the import graph of your package statically and checks it against ",[87,126,127],{},"contracts"," declared in ",[14,130,131],{},"pyproject.toml",":",[134,135,140],"pre",{"className":136,"code":137,"language":138,"meta":139,"style":139},"language-toml shiki shiki-themes github-light github-dark","# pyproject.toml\n[tool.importlinter]\nroot_packages = [\"mytool\"]\ninclude_external_packages = true\n\n[[tool.importlinter.contracts]]\nname = \"Layered architecture\"\ntype = \"layers\"\nlayers = [\n  \"mytool.cli\",\n  \"mytool.services\",\n  \"mytool.core\",\n]\n\n[[tool.importlinter.contracts]]\nname = \"Core has no framework or heavy dependencies\"\ntype = \"forbidden\"\nsource_modules = [\"mytool.core\"]\nforbidden_modules = [\"typer\", \"click\", \"rich\", \"httpx\", \"keyring\"]\n\n[[tool.importlinter.contracts]]\nname = \"Services do not depend on the CLI framework\"\ntype = \"forbidden\"\nsource_modules = [\"mytool.services\"]\nforbidden_modules = [\"typer\", \"click\", \"rich\"]\n\n[[tool.importlinter.contracts]]\nname = \"Commands are independent\"\ntype = \"independence\"\nmodules = [\n  \"mytool.cli.commands.deploy\",\n  \"mytool.cli.commands.report\",\n  \"mytool.cli.commands.auth\",\n]\n","toml","",[14,141,142,151,170,182,192,199,218,227,236,242,251,259,267,272,277,294,302,310,321,352,357,374,382,389,399,416,421,438,446,454,460,468,476,484],{"__ignoreMap":139},[143,144,147],"span",{"class":145,"line":146},"line",1,[143,148,150],{"class":149},"sJ8bj","# pyproject.toml\n",[143,152,154,158,162,164,167],{"class":145,"line":153},2,[143,155,157],{"class":156},"sVt8B","[",[143,159,161],{"class":160},"sScJk","tool",[143,163,35],{"class":156},[143,165,166],{"class":160},"importlinter",[143,168,169],{"class":156},"]\n",[143,171,173,176,180],{"class":145,"line":172},3,[143,174,175],{"class":156},"root_packages = [",[143,177,179],{"class":178},"sZZnC","\"mytool\"",[143,181,169],{"class":156},[143,183,185,188],{"class":145,"line":184},4,[143,186,187],{"class":156},"include_external_packages = ",[143,189,191],{"class":190},"sj4cs","true\n",[143,193,195],{"class":145,"line":194},5,[143,196,198],{"emptyLinePlaceholder":197},true,"\n",[143,200,202,205,207,209,211,213,215],{"class":145,"line":201},6,[143,203,204],{"class":156},"[[",[143,206,161],{"class":160},[143,208,35],{"class":156},[143,210,166],{"class":160},[143,212,35],{"class":156},[143,214,127],{"class":160},[143,216,217],{"class":156},"]]\n",[143,219,221,224],{"class":145,"line":220},7,[143,222,223],{"class":156},"name = ",[143,225,226],{"class":178},"\"Layered architecture\"\n",[143,228,230,233],{"class":145,"line":229},8,[143,231,232],{"class":156},"type = ",[143,234,235],{"class":178},"\"layers\"\n",[143,237,239],{"class":145,"line":238},9,[143,240,241],{"class":156},"layers = [\n",[143,243,245,248],{"class":145,"line":244},10,[143,246,247],{"class":178},"  \"mytool.cli\"",[143,249,250],{"class":156},",\n",[143,252,254,257],{"class":145,"line":253},11,[143,255,256],{"class":178},"  \"mytool.services\"",[143,258,250],{"class":156},[143,260,262,265],{"class":145,"line":261},12,[143,263,264],{"class":178},"  \"mytool.core\"",[143,266,250],{"class":156},[143,268,270],{"class":145,"line":269},13,[143,271,169],{"class":156},[143,273,275],{"class":145,"line":274},14,[143,276,198],{"emptyLinePlaceholder":197},[143,278,280,282,284,286,288,290,292],{"class":145,"line":279},15,[143,281,204],{"class":156},[143,283,161],{"class":160},[143,285,35],{"class":156},[143,287,166],{"class":160},[143,289,35],{"class":156},[143,291,127],{"class":160},[143,293,217],{"class":156},[143,295,297,299],{"class":145,"line":296},16,[143,298,223],{"class":156},[143,300,301],{"class":178},"\"Core has no framework or heavy dependencies\"\n",[143,303,305,307],{"class":145,"line":304},17,[143,306,232],{"class":156},[143,308,309],{"class":178},"\"forbidden\"\n",[143,311,313,316,319],{"class":145,"line":312},18,[143,314,315],{"class":156},"source_modules = [",[143,317,318],{"class":178},"\"mytool.core\"",[143,320,169],{"class":156},[143,322,324,327,330,332,335,337,340,342,345,347,350],{"class":145,"line":323},19,[143,325,326],{"class":156},"forbidden_modules = [",[143,328,329],{"class":178},"\"typer\"",[143,331,51],{"class":156},[143,333,334],{"class":178},"\"click\"",[143,336,51],{"class":156},[143,338,339],{"class":178},"\"rich\"",[143,341,51],{"class":156},[143,343,344],{"class":178},"\"httpx\"",[143,346,51],{"class":156},[143,348,349],{"class":178},"\"keyring\"",[143,351,169],{"class":156},[143,353,355],{"class":145,"line":354},20,[143,356,198],{"emptyLinePlaceholder":197},[143,358,360,362,364,366,368,370,372],{"class":145,"line":359},21,[143,361,204],{"class":156},[143,363,161],{"class":160},[143,365,35],{"class":156},[143,367,166],{"class":160},[143,369,35],{"class":156},[143,371,127],{"class":160},[143,373,217],{"class":156},[143,375,377,379],{"class":145,"line":376},22,[143,378,223],{"class":156},[143,380,381],{"class":178},"\"Services do not depend on the CLI framework\"\n",[143,383,385,387],{"class":145,"line":384},23,[143,386,232],{"class":156},[143,388,309],{"class":178},[143,390,392,394,397],{"class":145,"line":391},24,[143,393,315],{"class":156},[143,395,396],{"class":178},"\"mytool.services\"",[143,398,169],{"class":156},[143,400,402,404,406,408,410,412,414],{"class":145,"line":401},25,[143,403,326],{"class":156},[143,405,329],{"class":178},[143,407,51],{"class":156},[143,409,334],{"class":178},[143,411,51],{"class":156},[143,413,339],{"class":178},[143,415,169],{"class":156},[143,417,419],{"class":145,"line":418},26,[143,420,198],{"emptyLinePlaceholder":197},[143,422,424,426,428,430,432,434,436],{"class":145,"line":423},27,[143,425,204],{"class":156},[143,427,161],{"class":160},[143,429,35],{"class":156},[143,431,166],{"class":160},[143,433,35],{"class":156},[143,435,127],{"class":160},[143,437,217],{"class":156},[143,439,441,443],{"class":145,"line":440},28,[143,442,223],{"class":156},[143,444,445],{"class":178},"\"Commands are independent\"\n",[143,447,449,451],{"class":145,"line":448},29,[143,450,232],{"class":156},[143,452,453],{"class":178},"\"independence\"\n",[143,455,457],{"class":145,"line":456},30,[143,458,459],{"class":156},"modules = [\n",[143,461,463,466],{"class":145,"line":462},31,[143,464,465],{"class":178},"  \"mytool.cli.commands.deploy\"",[143,467,250],{"class":156},[143,469,471,474],{"class":145,"line":470},32,[143,472,473],{"class":178},"  \"mytool.cli.commands.report\"",[143,475,250],{"class":156},[143,477,479,482],{"class":145,"line":478},33,[143,480,481],{"class":178},"  \"mytool.cli.commands.auth\"",[143,483,250],{"class":156},[143,485,487],{"class":145,"line":486},34,[143,488,169],{"class":156},[10,490,491,492,495,496,499],{},"Run it with ",[14,493,494],{},"uv run lint-imports",". ",[14,497,498],{},"include_external_packages = true"," is what makes the forbidden contracts on third-party packages work; without it, import-linter only analyses imports within your own package.",[79,501],{"name":502},"lint-contracts-matrix",[504,505,507],"h3",{"id":506},"what-each-contract-protects","What each contract protects",[10,509,510,513,514,517,518,521],{},[87,511,512],{},"Layers"," stop the most damaging kind of erosion: a lower layer reaching up. If ",[14,515,516],{},"mytool.core.plan"," imports ",[14,519,520],{},"mytool.cli.output"," for a formatting helper, core now depends on the CLI and everything it imports. The layers contract fails with the exact chain of imports responsible.",[10,523,524,527,528,531,532,535,536,35],{},[87,525,526],{},"Forbidden (core)"," keeps heavy and framework libraries out of the code every command loads. This is the contract most CLIs benefit from, because it doubles as a ",[87,529,530],{},"startup-time guard",": Rich, httpx and keyring each add tens of milliseconds of import time, and a single transitive import from core means paying that on every ",[14,533,534],{},"--help"," and every Tab press. The broader techniques are in ",[31,537,539],{"href":538},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002F","CLI startup performance and lazy loading",[10,541,542,545,546,549],{},[87,543,544],{},"Forbidden (services)"," keeps presentation out of the middle layer. A service that raises ",[14,547,548],{},"typer.Exit"," or prints with Rich cannot be reused by anything but this CLI; one that raises its own exceptions and returns data can.",[10,551,552,555,556,559,560,563,564,567,568,35],{},[87,553,554],{},"Independence"," stops commands from importing each other. When ",[14,557,558],{},"report"," imports a helper from ",[14,561,562],{},"deploy",", the two are coupled, and lazy-loading one loads both. Shared helpers belong in ",[14,565,566],{},"services"," or ",[14,569,101],{},[37,571,573],{"id":572},"reading-a-failure","Reading a failure",[79,575],{"name":576},"lint-lint-imports-terminal",[10,578,579,580,583,584,587,588,591],{},"import-linter reports indirect chains, which is what makes it more than a grep: here ",[14,581,582],{},"core.plan"," never imports Rich itself, but it imports ",[14,585,586],{},"core.display",", which does. The fix is to move the display helper up into the CLI layer and have core return data instead. When a violation is known and cannot be fixed immediately, the contract can list it under ",[14,589,590],{},"ignore_imports"," — keep that list short and treat each entry as debt with an owner.",[37,593,595],{"id":594},"a-test-suite-fallback","A test-suite fallback",[10,597,598,599,132],{},"If adding another tool is not an option, a small test can enforce the most important rule — \"core does not import these packages\" — by actually importing core in a clean interpreter and inspecting ",[14,600,601],{},"sys.modules",[134,603,607],{"className":604,"code":605,"language":606,"meta":139,"style":139},"language-python shiki shiki-themes github-light github-dark","# tests\u002Ftest_boundaries.py\nimport json\nimport subprocess\nimport sys\n\nFORBIDDEN = {\"typer\", \"click\", \"rich\", \"httpx\", \"keyring\"}\n\n\ndef test_core_imports_no_heavy_packages():\n    code = (\n        \"import json, sys\\n\"\n        \"import mytool.core\\n\"\n        \"import pkgutil, importlib\\n\"\n        \"for m in pkgutil.walk_packages(mytool.core.__path__, 'mytool.core.'):\\n\"\n        \"    importlib.import_module(m.name)\\n\"\n        \"print(json.dumps(sorted({n.split('.')[0] for n in sys.modules})))\\n\"\n    )\n    out = subprocess.run([sys.executable, \"-c\", code], capture_output=True, text=True, check=True)\n    loaded = set(json.loads(out.stdout))\n    assert not (loaded & FORBIDDEN), f\"core pulled in: {sorted(loaded & FORBIDDEN)}\"\n","python",[14,608,609,614,623,630,637,641,673,677,681,692,703,714,723,732,741,750,759,764,810,823],{"__ignoreMap":139},[143,610,611],{"class":145,"line":146},[143,612,613],{"class":149},"# tests\u002Ftest_boundaries.py\n",[143,615,616,620],{"class":145,"line":153},[143,617,619],{"class":618},"szBVR","import",[143,621,622],{"class":156}," json\n",[143,624,625,627],{"class":145,"line":172},[143,626,619],{"class":618},[143,628,629],{"class":156}," subprocess\n",[143,631,632,634],{"class":145,"line":184},[143,633,619],{"class":618},[143,635,636],{"class":156}," sys\n",[143,638,639],{"class":145,"line":194},[143,640,198],{"emptyLinePlaceholder":197},[143,642,643,646,649,652,654,656,658,660,662,664,666,668,670],{"class":145,"line":201},[143,644,645],{"class":190},"FORBIDDEN",[143,647,648],{"class":618}," =",[143,650,651],{"class":156}," {",[143,653,329],{"class":178},[143,655,51],{"class":156},[143,657,334],{"class":178},[143,659,51],{"class":156},[143,661,339],{"class":178},[143,663,51],{"class":156},[143,665,344],{"class":178},[143,667,51],{"class":156},[143,669,349],{"class":178},[143,671,672],{"class":156},"}\n",[143,674,675],{"class":145,"line":220},[143,676,198],{"emptyLinePlaceholder":197},[143,678,679],{"class":145,"line":229},[143,680,198],{"emptyLinePlaceholder":197},[143,682,683,686,689],{"class":145,"line":238},[143,684,685],{"class":618},"def",[143,687,688],{"class":160}," test_core_imports_no_heavy_packages",[143,690,691],{"class":156},"():\n",[143,693,694,697,700],{"class":145,"line":244},[143,695,696],{"class":156},"    code ",[143,698,699],{"class":618},"=",[143,701,702],{"class":156}," (\n",[143,704,705,708,711],{"class":145,"line":253},[143,706,707],{"class":178},"        \"import json, sys",[143,709,710],{"class":190},"\\n",[143,712,713],{"class":178},"\"\n",[143,715,716,719,721],{"class":145,"line":261},[143,717,718],{"class":178},"        \"import mytool.core",[143,720,710],{"class":190},[143,722,713],{"class":178},[143,724,725,728,730],{"class":145,"line":269},[143,726,727],{"class":178},"        \"import pkgutil, importlib",[143,729,710],{"class":190},[143,731,713],{"class":178},[143,733,734,737,739],{"class":145,"line":274},[143,735,736],{"class":178},"        \"for m in pkgutil.walk_packages(mytool.core.__path__, 'mytool.core.'):",[143,738,710],{"class":190},[143,740,713],{"class":178},[143,742,743,746,748],{"class":145,"line":279},[143,744,745],{"class":178},"        \"    importlib.import_module(m.name)",[143,747,710],{"class":190},[143,749,713],{"class":178},[143,751,752,755,757],{"class":145,"line":296},[143,753,754],{"class":178},"        \"print(json.dumps(sorted({n.split('.')[0] for n in sys.modules})))",[143,756,710],{"class":190},[143,758,713],{"class":178},[143,760,761],{"class":145,"line":304},[143,762,763],{"class":156},"    )\n",[143,765,766,769,771,774,777,780,784,786,789,791,794,796,798,800,803,805,807],{"class":145,"line":312},[143,767,768],{"class":156},"    out ",[143,770,699],{"class":618},[143,772,773],{"class":156}," subprocess.run([sys.executable, ",[143,775,776],{"class":178},"\"-c\"",[143,778,779],{"class":156},", code], ",[143,781,783],{"class":782},"s4XuR","capture_output",[143,785,699],{"class":618},[143,787,788],{"class":190},"True",[143,790,51],{"class":156},[143,792,793],{"class":782},"text",[143,795,699],{"class":618},[143,797,788],{"class":190},[143,799,51],{"class":156},[143,801,802],{"class":782},"check",[143,804,699],{"class":618},[143,806,788],{"class":190},[143,808,809],{"class":156},")\n",[143,811,812,815,817,820],{"class":145,"line":323},[143,813,814],{"class":156},"    loaded ",[143,816,699],{"class":618},[143,818,819],{"class":190}," set",[143,821,822],{"class":156},"(json.loads(out.stdout))\n",[143,824,825,828,831,834,837,840,843,846,849,852,855,857,859,862,865],{"class":145,"line":354},[143,826,827],{"class":618},"    assert",[143,829,830],{"class":618}," not",[143,832,833],{"class":156}," (loaded ",[143,835,836],{"class":618},"&",[143,838,839],{"class":190}," FORBIDDEN",[143,841,842],{"class":156},"), ",[143,844,845],{"class":618},"f",[143,847,848],{"class":178},"\"core pulled in: ",[143,850,851],{"class":190},"{sorted",[143,853,854],{"class":156},"(loaded ",[143,856,836],{"class":618},[143,858,839],{"class":190},[143,860,861],{"class":156},")",[143,863,864],{"class":190},"}",[143,866,713],{"class":178},[10,868,869,870,872,873,876],{},"Running in a subprocess gives a clean ",[14,871,601],{}," unaffected by whatever the test session already imported. This checks runtime behaviour rather than the static graph, which also catches imports made through ",[14,874,875],{},"importlib"," or plugins — a useful complement even when import-linter is in place.",[37,878,880],{"id":879},"measuring-the-payoff","Measuring the payoff",[10,882,883],{},"The same boundary shows up in startup time, and it is worth measuring once so the benefit is concrete:",[134,885,889],{"className":886,"code":887,"language":888,"meta":139,"style":139},"language-bash shiki shiki-themes github-light github-dark","$ uv run python -X importtime -c \"import mytool.core\" 2>&1 | tail -1\nimport time:       312 |       4870 | mytool.core\n$ uv run python -X importtime -c \"import mytool.cli\" 2>&1 | tail -1\nimport time:      1204 |      61230 | mytool.cli\n","bash",[14,890,891,929,949,976],{"__ignoreMap":139},[143,892,893,896,899,902,905,908,911,914,917,920,923,926],{"class":145,"line":146},[143,894,895],{"class":160},"$",[143,897,898],{"class":178}," uv",[143,900,901],{"class":178}," run",[143,903,904],{"class":178}," python",[143,906,907],{"class":190}," -X",[143,909,910],{"class":178}," importtime",[143,912,913],{"class":190}," -c",[143,915,916],{"class":178}," \"import mytool.core\"",[143,918,919],{"class":618}," 2>&1",[143,921,922],{"class":618}," |",[143,924,925],{"class":160}," tail",[143,927,928],{"class":190}," -1\n",[143,930,931,933,936,939,941,944,946],{"class":145,"line":153},[143,932,619],{"class":160},[143,934,935],{"class":178}," time:",[143,937,938],{"class":190},"       312",[143,940,922],{"class":618},[143,942,943],{"class":160},"       4870",[143,945,922],{"class":618},[143,947,948],{"class":160}," mytool.core\n",[143,950,951,953,955,957,959,961,963,965,968,970,972,974],{"class":145,"line":172},[143,952,895],{"class":160},[143,954,898],{"class":178},[143,956,901],{"class":178},[143,958,904],{"class":178},[143,960,907],{"class":190},[143,962,910],{"class":178},[143,964,913],{"class":190},[143,966,967],{"class":178}," \"import mytool.cli\"",[143,969,919],{"class":618},[143,971,922],{"class":618},[143,973,925],{"class":160},[143,975,928],{"class":190},[143,977,978,980,982,985,987,990,992],{"class":145,"line":184},[143,979,619],{"class":160},[143,981,935],{"class":178},[143,983,984],{"class":190},"      1204",[143,986,922],{"class":618},[143,988,989],{"class":160},"      61230",[143,991,922],{"class":618},[143,993,994],{"class":160}," mytool.cli\n",[10,996,997,998,1002,1003,1006],{},"The cumulative column is in microseconds: importing core takes about 5 ms, importing the full CLI layer about 61 ms. Keeping core free of framework imports is what keeps that first number small. ",[31,999,1001],{"href":1000},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fprofiling-python-cli-startup-time\u002F","Profiling Python CLI startup time"," covers reading ",[14,1004,1005],{},"-X importtime"," output in detail.",[37,1008,1010],{"id":1009},"ux-considerations","UX considerations",[10,1012,1013],{},"For the developers working in the codebase:",[42,1015,1016,1022,1031,1037],{},[45,1017,1018,1021],{},[87,1019,1020],{},"Name contracts after the rule, not the tool."," \"Core has no framework dependencies\" tells a contributor what they broke; \"contract 2\" does not.",[45,1023,1024,1027,1028,1030],{},[87,1025,1026],{},"Explain the why near the contract."," A comment in ",[14,1029,131],{}," — \"core is imported by every command; keep it light\" — turns a failure into a lesson rather than an obstacle.",[45,1032,1033,1036],{},[87,1034,1035],{},"Start with one contract."," The forbidden-imports contract on core is the highest value and least controversial. Add layers and independence once the structure they describe actually exists.",[45,1038,1039,1042,1043,1046],{},[87,1040,1041],{},"Run it where people will see it."," In CI's lint job and as a pre-commit hook (",[14,1044,1045],{},"lint-imports"," is fast enough), so violations are caught in the pull request that introduces them.",[37,1048,1050],{"id":1049},"testing-the-behaviour","Testing the behaviour",[10,1052,1053],{},"To confirm the contracts work, break one deliberately:",[134,1055,1057],{"className":886,"code":1056,"language":888,"meta":139,"style":139},"echo \"from rich import print  # temporary\" >> src\u002Fmytool\u002Fcore\u002Fplan.py\nuv run lint-imports        # expect: \"Core has no framework ...\" BROKEN\ngit checkout src\u002Fmytool\u002Fcore\u002Fplan.py\n",[14,1058,1059,1073,1086],{"__ignoreMap":139},[143,1060,1061,1064,1067,1070],{"class":145,"line":146},[143,1062,1063],{"class":190},"echo",[143,1065,1066],{"class":178}," \"from rich import print  # temporary\"",[143,1068,1069],{"class":618}," >>",[143,1071,1072],{"class":178}," src\u002Fmytool\u002Fcore\u002Fplan.py\n",[143,1074,1075,1078,1080,1083],{"class":145,"line":153},[143,1076,1077],{"class":160},"uv",[143,1079,901],{"class":178},[143,1081,1082],{"class":178}," lint-imports",[143,1084,1085],{"class":149},"        # expect: \"Core has no framework ...\" BROKEN\n",[143,1087,1088,1091,1094],{"class":145,"line":172},[143,1089,1090],{"class":160},"git",[143,1092,1093],{"class":178}," checkout",[143,1095,1072],{"class":178},[10,1097,1098,1099,1102,1103,1106],{},"A contract that has never been seen to fail may be misconfigured — a typo in a module name, or ",[14,1100,1101],{},"include_external_packages"," missing so external imports are invisible. ",[14,1104,1105],{},"lint-imports --verbose"," prints the graph it built and the modules each contract considered, which helps diagnose both.",[37,1108,1110],{"id":1109},"conclusion","Conclusion",[10,1112,1113,1114,1116],{},"Architecture rules that live only in a document erode one convenient import at a time. ",[14,1115,28],{}," turns them into contracts checked on every commit: layers so imports point downward, forbidden modules so core stays free of frameworks and heavy libraries, and independence so commands do not tangle together. The same boundaries keep startup fast and core reusable, and a small runtime test can back them up. Start with the forbidden contract on core; it pays for itself the first time it fails.",[37,1118,1120],{"id":1119},"frequently-asked-questions","Frequently asked questions",[504,1122,1124],{"id":1123},"does-import-linter-see-imports-inside-functions","Does import-linter see imports inside functions?",[10,1126,1127,1128,1131,1132,1135],{},"Yes. It analyses all import statements in each module, including those inside functions, which is what you want — a lazy import from core to Rich is still a dependency. ",[14,1129,1130],{},"TYPE_CHECKING","-only imports can be excluded with the ",[14,1133,1134],{},"exclude_type_checking_imports"," option.",[504,1137,1139],{"id":1138},"how-do-plugins-fit-into-the-layers","How do plugins fit into the layers?",[10,1141,1142,1143,1145,1146,1149,1150,1152,1153,35],{},"Treat plugins as a separate top-level layer that may import your public API (usually ",[14,1144,57],{}," and a small ",[14,1147,1148],{},"mytool.plugin_api"," module) but not internals. A forbidden contract from plugin packages to ",[14,1151,50],{}," expresses that. See ",[31,1154,1156],{"href":1155},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fversioning-a-plugin-api\u002F","versioning a plugin API",[504,1158,1160],{"id":1159},"what-if-two-commands-genuinely-share-code","What if two commands genuinely share code?",[10,1162,1163,1164,567,1166,1168],{},"Move the shared code down into ",[14,1165,566],{},[14,1167,101],{},", where both can import it without depending on each other. The independence contract exists precisely to force that move.",[504,1170,1172],{"id":1171},"how-do-i-introduce-contracts-into-a-codebase-that-already-violates-them","How do I introduce contracts into a codebase that already violates them?",[10,1174,1175,1176,1178,1179,1181,1182,1186],{},"Write the contract as you want it, run ",[14,1177,1045],{},", and copy each reported violation into the contract's ",[14,1180,590],{}," list with a comment naming who will fix it. The contract then passes and immediately blocks any ",[1183,1184,1185],"em",{},"new"," violation, while the ignore list shrinks as the old ones are untangled. Deleting the last entry is a satisfying pull request.",[504,1188,1190],{"id":1189},"is-this-worth-it-for-a-small-cli","Is this worth it for a small CLI?",[10,1192,1193],{},"For a single-file script, no. Once a CLI has more than a handful of commands or more than one maintainer, a single forbidden contract on core is five lines of configuration and prevents the slowest-to-fix kind of decay.",[37,1195,1197],{"id":1196},"related","Related",[42,1199,1200,1206,1212,1218,1223],{},[45,1201,1202,1203],{},"Up: ",[31,1204,1205],{"href":33},"Linting and type-checking CLI code",[45,1207,1208],{},[31,1209,1211],{"href":1210},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fconfiguring-ruff-for-a-cli-project\u002F","Configuring Ruff for a CLI project",[45,1213,1214],{},[31,1215,1217],{"href":1216},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Ftype-checking-click-and-typer-code-with-mypy\u002F","Type-checking Click and Typer code with mypy",[45,1219,1220],{},[31,1221,1222],{"href":61},"How to structure a large Python CLI project",[45,1224,1225],{},[31,1226,1228],{"href":1227},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Flazy-loading-subcommands-for-faster-startup\u002F","Lazy-loading subcommands for faster startup",[1230,1231,1232],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}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 .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}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 .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}",{"title":139,"searchDepth":153,"depth":153,"links":1234},[1235,1236,1237,1240,1241,1242,1243,1244,1245,1246,1253],{"id":39,"depth":153,"text":40},{"id":73,"depth":153,"text":74},{"id":118,"depth":153,"text":119,"children":1238},[1239],{"id":506,"depth":172,"text":507},{"id":572,"depth":153,"text":573},{"id":594,"depth":153,"text":595},{"id":879,"depth":153,"text":880},{"id":1009,"depth":153,"text":1010},{"id":1049,"depth":153,"text":1050},{"id":1109,"depth":153,"text":1110},{"id":1119,"depth":153,"text":1120,"children":1247},[1248,1249,1250,1251,1252],{"id":1123,"depth":172,"text":1124},{"id":1138,"depth":172,"text":1139},{"id":1159,"depth":172,"text":1160},{"id":1171,"depth":172,"text":1172},{"id":1189,"depth":172,"text":1190},{"id":1196,"depth":153,"text":1197},"2026-09-18","Keep a Python CLI’s layers separate with import-linter: layers, forbidden and independence contracts, keeping heavy libraries out of core, and a startup-time guard.","advanced",false,"md",{},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fenforcing-import-boundaries-in-a-cli-codebase",{"title":5,"description":1255},"project-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fenforcing-import-boundaries-in-a-cli-codebase\u002Findex",[1264,28,1265,1266],"architecture","code-quality","startup-performance","_8jMavww_ubPEBK5fSAgXkaJFG8DwAnuwrADFryTUoA",[1269,1272,1275,1278,1281,1284,1287,1290,1293,1296,1299,1302,1305,1308,1311,1314,1317,1320,1323,1326,1329,1332,1335,1338,1341,1344,1347,1350,1353,1356,1359,1362,1365,1368,1371,1374,1377,1380,1383,1386,1389,1392,1395,1398,1401,1404,1407,1410,1413,1416,1419,1422,1425,1428,1431,1434,1437,1440,1443,1446,1449,1452,1455,1458,1461,1464,1467,1470,1473,1476,1479,1482,1485,1488,1491,1494,1497,1500,1503,1506,1509,1512,1515,1518,1521,1524,1527,1530,1533,1536,1539,1542,1545,1548,1551,1554,1557,1560,1563,1566,1569,1572,1575,1578,1581,1584,1587,1590,1593,1596,1599,1602,1605,1608,1611,1614,1617,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,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,1813],{"path":1270,"title":1271},"\u002Fabout","About Python CLI Toolcraft",{"path":1273,"title":1274},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies","Advanced Argument Validation Strategies",{"path":1276,"title":1277},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fparsing-nested-json-arguments-in-python-clis","Parsing Nested JSON Args in Python CLIs",{"path":1279,"title":1280},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-dependent-and-conflicting-options","Validating Dependent and Conflicting CLI Options",{"path":1282,"title":1283},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-file-and-directory-paths-in-clis","Validating File and Directory Paths in CLIs",{"path":1285,"title":1286},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fwriting-custom-click-parameter-types","Writing Custom Click Parameter Types",{"path":1288,"title":1289},"\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":1291,"title":1292},"\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":1294,"title":1295},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual","Building Terminal UIs with Textual for Python CLIs",{"path":1297,"title":1298},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Ftesting-textual-apps-with-pilot","Testing Textual Apps with Pilot",{"path":1300,"title":1301},"\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":1303,"title":1304},"\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":1306,"title":1307},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation","CLI Help Output and Documentation",{"path":1309,"title":1310},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fversioning-and-deprecating-cli-flags","Versioning and Deprecating CLI Flags",{"path":1312,"title":1313},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fwriting-help-text-users-actually-read","Writing Help Text Users Actually Read",{"path":1315,"title":1316},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fadapting-output-to-terminal-width","Adapting Python CLI Output to Terminal Width",{"path":1318,"title":1319},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fdetecting-ci-environments-and-non-interactive-shells","Detecting CI Environments and Non-Interactive Shells",{"path":1321,"title":1322},"\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":1324,"title":1325},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility","Cross-Platform Terminal Compatibility for Python CLIs",{"path":1327,"title":1328},"\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":1330,"title":1331},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fchoosing-exit-codes-for-cli-tools","Choosing Exit Codes for CLI Tools",{"path":1333,"title":1334},"\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":1336,"title":1337},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Ffriendly-error-messages-and-tracebacks","Friendly Error Messages and Tracebacks",{"path":1339,"title":1340},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fhandling-keyboard-interrupt-cleanly","Handling Keyboard Interrupt Cleanly",{"path":1342,"title":1343},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes","Error Handling and Exit Codes for CLIs",{"path":1345,"title":1346},"\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":1348,"title":1349},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Fconfig-precedence-flags-env-files-defaults","Config Precedence: Flags, Env, Files, Defaults",{"path":1351,"title":1352},"\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":1354,"title":1355},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars","Handling Config Files and Env Vars in CLIs",{"path":1357,"title":1358},"\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":1360,"title":1361},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Freading-toml-config-with-tomllib","Reading TOML Config with tomllib in Python CLIs",{"path":1363,"title":1364},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Ftyped-settings-with-pydantic-settings","Typed Settings with pydantic-settings in Python CLIs",{"path":1366,"title":1367},"\u002Fadvanced-input-parsing-user-experience","Advanced Input Parsing for Python CLIs",{"path":1369,"title":1370},"\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":1372,"title":1373},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Fbuilding-interactive-prompts-and-menus","Building Interactive Prompts and Menus in Python CLIs",{"path":1375,"title":1376},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich","Interactive Terminal UI with Rich",{"path":1378,"title":1379},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Flive-dashboards-with-rich-live","Live Dashboards with Rich Live in Python CLIs",{"path":1381,"title":1382},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Frendering-tables-and-json-with-rich","Rendering Tables and JSON with Rich",{"path":1384,"title":1385},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Ftheming-rich-output-consistently","Theming Rich Output Consistently in Python CLIs",{"path":1387,"title":1388},"\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":1390,"title":1391},"\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":1393,"title":1394},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis","Shell Completion for Python CLIs",{"path":1396,"title":1397},"\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":1399,"title":1400},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Ftesting-shell-completion-in-python-clis","Testing Shell Completion in Python CLIs",{"path":1402,"title":1403},"\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":1405,"title":1406},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fadding-verbose-and-quiet-logging-flags","Adding Verbose and Quiet Logging Flags",{"path":1408,"title":1409},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps","Structured Logging for CLI Apps",{"path":1411,"title":1412},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fstructured-json-logging-in-python-clis","Structured JSON Logging in Python CLIs",{"path":1414,"title":1415},"\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":1417,"title":1418},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fdetecting-tty-and-adapting-output","Detecting a TTY and Adapting Output",{"path":1420,"title":1421},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Femitting-json-output-for-scripting","Emitting JSON Output for Scripting",{"path":1423,"title":1424},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fhandling-broken-pipe-and-sigpipe","Handling Broken Pipe and SIGPIPE",{"path":1426,"title":1427},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes","Working with stdin, stdout and Pipes",{"path":1429,"title":1430},"\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":1432,"title":1433},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Freading-piped-input-in-python-clis","Reading Piped Input in Python CLIs",{"path":1435,"title":1436},"\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":1438,"title":1439},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fdownloading-files-with-progress-in-python","Downloading Files with Progress in Python CLIs",{"path":1441,"title":1442},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis","Calling HTTP APIs from Python CLIs",{"path":1444,"title":1445},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Foauth-device-flow-login-for-clis","OAuth Device Flow Login for Python CLIs",{"path":1447,"title":1448},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fpaginating-api-results-in-a-cli","Paginating API Results in a Python CLI",{"path":1450,"title":1451},"\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":1453,"title":1454},"\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":1456,"title":1457},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis","Concurrency and Async in Python CLIs",{"path":1459,"title":1460},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fmultiprocessing-for-cpu-bound-cli-tasks","Multiprocessing for CPU-Bound CLI Tasks",{"path":1462,"title":1463},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fparallelising-cli-work-with-thread-pools","Parallelising CLI Work with Thread Pools",{"path":1465,"title":1466},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Frate-limiting-concurrent-requests-in-clis","Rate-Limiting Concurrent Requests in Python CLIs",{"path":1468,"title":1469},"\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":1471,"title":1472},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fcross-platform-paths-with-pathlib","Cross-Platform Paths with pathlib in CLIs",{"path":1474,"title":1475},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Ffile-locking-for-concurrent-cli-runs","File Locking for Concurrent CLI Runs in Python",{"path":1477,"title":1478},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes","Filesystem Paths and Atomic Writes for CLIs",{"path":1480,"title":1481},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fsafe-temporary-files-and-directories","Safe Temporary Files and Directories in CLIs",{"path":1483,"title":1484},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fstoring-app-data-with-platformdirs","Storing CLI App Data with platformdirs",{"path":1486,"title":1487},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fwriting-files-atomically-in-python-clis","Writing Files Atomically in Python CLIs",{"path":1489,"title":1490},"\u002Fcli-runtime-systems-integration","CLI Runtime & Systems Integration for Python",{"path":1492,"title":1493},"\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":1495,"title":1496},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fhandling-sigterm-and-graceful-shutdown","Handling SIGTERM and Graceful Shutdown in CLIs",{"path":1498,"title":1499},"\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":1501,"title":1502},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis","Long-Running and Watch-Mode Python CLIs",{"path":1504,"title":1505},"\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":1507,"title":1508},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Favoiding-shell-injection-in-python-clis","Avoiding Shell Injection in Python CLIs",{"path":1510,"title":1511},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fcalling-external-commands-safely-with-subprocess","Calling External Commands Safely with subprocess",{"path":1513,"title":1514},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fhandling-subprocess-timeouts-and-exit-codes","Handling Subprocess Timeouts and Exit Codes",{"path":1516,"title":1517},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis","Running Subprocesses from Python CLIs",{"path":1519,"title":1520},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fstreaming-subprocess-output-in-real-time","Streaming Subprocess Output in Real Time",{"path":1522,"title":1523},"\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":1525,"title":1526},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis","Secrets and Credentials in Python CLIs",{"path":1528,"title":1529},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fprompting-for-passwords-securely","Prompting for Passwords Securely in Python CLIs",{"path":1531,"title":1532},"\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":1534,"title":1535},"\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":1537,"title":1538},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fstoring-tokens-with-keyring","Storing CLI Tokens Securely with keyring",{"path":1540,"title":1541},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fsupporting-multiple-profiles-and-accounts","Supporting Multiple Profiles and Accounts in CLIs",{"path":1543,"title":1544},"\u002F","Python CLI Toolcraft",{"path":1546,"title":1547},"\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":1549,"title":1550},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading","CLI Startup Performance and Lazy Loading",{"path":1552,"title":1553},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Flazy-loading-subcommands-for-faster-startup","Lazy Loading Subcommands for Faster Startup",{"path":1555,"title":1556},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fprofiling-python-cli-startup-time","Profiling Python CLI Startup Time",{"path":1558,"title":1559},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Freducing-cli-dependency-weight","Reducing CLI Dependency Weight",{"path":1561,"title":1562},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-subparsers-for-subcommands","argparse Subparsers for Subcommands",{"path":1564,"title":1565},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-vs-click-vs-typer-comparison","argparse vs Click vs Typer Compared",{"path":1567,"title":1568},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse","Command-Line Parsing with argparse",{"path":1570,"title":1571},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmigrating-from-argparse-to-typer","Migrating from argparse to Typer",{"path":1573,"title":1574},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmutually-exclusive-options-in-argparse","Mutually Exclusive Options in argparse",{"path":1576,"title":1577},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fwriting-custom-argparse-actions","Writing Custom argparse Actions in Python",{"path":1579,"title":1580},"\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":1582,"title":1583},"\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":1585,"title":1586},"\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":1588,"title":1589},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions","Designing CLI Interfaces and Conventions in Python",{"path":1591,"title":1592},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fnaming-commands-and-flags-consistently","Naming Commands and Flags Consistently in Python CLIs",{"path":1594,"title":1595},"\u002Fmodern-python-cli-frameworks-architecture","Python CLI Frameworks and Architecture",{"path":1597,"title":1598},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fdiscovering-plugins-with-entry-points","Discovering Plugins with Entry Points in Python CLIs",{"path":1600,"title":1601},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fhook-based-plugins-with-pluggy","Hook-Based Plugins for Python CLIs with pluggy",{"path":1603,"title":1604},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis","Plugin Architectures for Extensible CLIs",{"path":1606,"title":1607},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fversioning-a-plugin-api","Versioning a Plugin API for a Python CLI",{"path":1609,"title":1610},"\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":1612,"title":1613},"\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":1615,"title":1616},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fdependency-injection-patterns-for-cli-commands","Dependency Injection Patterns for CLI Commands",{"path":1618,"title":1619},"\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":1621,"title":1622},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis","Structuring Multi-Command Python CLIs",{"path":1624,"title":1625},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-common-options-across-commands","Sharing Common Options Across Python CLI Commands",{"path":1627,"title":1628},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-state-with-click-context-objects","Sharing State with Click Context Objects",{"path":1630,"title":1631},"\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":1633,"title":1634},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications","Testing Python CLI Applications",{"path":1636,"title":1637},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fmeasuring-cli-test-coverage","Measuring CLI Test Coverage",{"path":1639,"title":1640},"\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":1642,"title":1643},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fproperty-based-testing-cli-arguments-with-hypothesis","Property-Based Testing CLI Arguments with Hypothesis",{"path":1645,"title":1646},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fsnapshot-testing-cli-output","Snapshot Testing CLI Output",{"path":1648,"title":1649},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-click-commands-with-clirunner","Testing Click Commands with CliRunner",{"path":1651,"title":1652},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-interactive-prompts-and-stdin","Testing Interactive Prompts and stdin",{"path":1654,"title":1655},"\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":1657,"title":1658},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fbuilding-dynamic-commands-in-click","Building Dynamic Commands in Click",{"path":1660,"title":1661},"\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":1663,"title":1664},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each","Typer vs Click: When to Use Each",{"path":1666,"title":1667},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Ftyper-callback-functions-explained","Typer callback functions explained",{"path":1669,"title":1670},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fusing-annotated-options-in-typer","Using Annotated Options in Typer",{"path":1672,"title":1673},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fautomating-releases-from-git-tags","Automating Python CLI Releases from Git Tags",{"path":1675,"title":1676},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fcaching-uv-dependencies-in-ci","Caching uv Dependencies in CI for Python CLIs",{"path":1678,"title":1679},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis","CI\u002FCD Pipelines for Python CLIs",{"path":1681,"title":1682},"\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":1684,"title":1685},"\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":1687,"title":1688},"\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":1690,"title":1691},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fbuilding-a-cookiecutter-template-for-typer-clis","Building a Cookiecutter Template for Typer CLIs",{"path":1693,"title":1694},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fcopier-vs-cookiecutter-for-cli-templates","Copier vs Cookiecutter for CLI Templates",{"path":1696,"title":1697},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter","CLI Project Scaffolding with Cookiecutter",{"path":1699,"title":1700},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fpost-generation-hooks-in-cli-templates","Post-Generation Hooks in Python CLI Templates",{"path":1702,"title":1703},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbuilding-cross-platform-release-binaries-in-ci","Building Cross-Platform Release Binaries in CI",{"path":1705,"title":1706},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbundling-a-python-cli-with-pyinstaller","Bundling a Python CLI with PyInstaller",{"path":1708,"title":1709},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fhomebrew-and-scoop-packaging-for-python-clis","Homebrew and Scoop Packaging for Python CLIs",{"path":1711,"title":1712},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries","Distributing CLIs as Standalone Binaries",{"path":1714,"title":1715},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fnuitka-vs-pyinstaller-for-python-clis","Nuitka vs PyInstaller for Python CLI Binaries",{"path":1717,"title":1718},"\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":1720,"title":1721},"\u002Fproject-setup-dependency-management","Project Setup & Dependency Management",{"path":1723,"title":1724},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fconfiguring-ruff-for-a-cli-project","Configuring Ruff for a Python CLI Project",{"path":1260,"title":5},{"path":1727,"title":1728},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code","Linting and Type-Checking Python CLI Code",{"path":1730,"title":1731},"\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":1733,"title":1734},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fautomating-changelogs-with-conventional-commits","Automating Changelogs with Conventional Commits",{"path":1736,"title":1737},"\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":1739,"title":1740},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fexposing-version-info-and-build-metadata","Exposing Version Info and Build Metadata",{"path":1742,"title":1743},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs","Managing CLI Versioning & Changelogs",{"path":1745,"title":1746},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fsemantic-versioning-policy-for-cli-tools","A Semantic Versioning Policy for CLI Tools",{"path":1748,"title":1749},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbuilding-wheels-and-sdists-for-python-clis","Building Wheels and sdists for Python CLIs",{"path":1751,"title":1752},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbundling-data-files-with-importlib-resources","Bundling Data Files with importlib.resources in CLIs",{"path":1754,"title":1755},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution","Packaging Python CLIs for Distribution",{"path":1757,"title":1758},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Finstalling-and-distributing-clis-with-pipx","Installing and Distributing CLIs with pipx",{"path":1760,"title":1761},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fpublishing-a-python-cli-to-pypi","Publishing a Python CLI to PyPI",{"path":1763,"title":1764},"\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":1766,"title":1767},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development","Poetry Workflows for CLI Development",{"path":1769,"title":1770},"\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":1772,"title":1773},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-dependency-groups-for-cli-tooling","Poetry Dependency Groups for CLI Tooling",{"path":1775,"title":1776},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-entry-points-and-scripts-for-clis","Poetry Entry Points and Scripts for CLIs",{"path":1778,"title":1779},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects","Pre-commit Hooks for CLI Projects",{"path":1781,"title":1782},"\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":1784,"title":1785},"\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":1787,"title":1788},"\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":1790,"title":1791},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management","uv for Python CLI Dependency Management",{"path":1793,"title":1794},"\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":1796,"title":1797},"\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":1799,"title":1800},"\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":1802,"title":1803},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis","uv Workspaces for Multi-Package Python CLIs",{"path":1805,"title":1806},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices","Python CLI Env Isolation Best Practices",{"path":1808,"title":1809},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fmanaging-virtual-environments-for-cross-platform-clis","Managing Python CLI Virtual Environments",{"path":1811,"title":1812},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fpinning-the-python-version-for-a-cli","Pinning the Python Version for a CLI",{"path":1814,"title":1815},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fsupporting-multiple-python-versions-with-nox","Supporting Multiple Python Versions with nox",1789736907490]