[{"data":1,"prerenderedAt":2103},["ShallowReactive",2],{"page-\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis\u002F":3,"content-directory":1259},{"id":4,"title":5,"body":6,"date":1245,"description":1246,"difficulty":1247,"draft":1248,"extension":1249,"meta":1250,"navigation":176,"path":1251,"seo":1252,"stem":1253,"tags":1254,"updated":1245,"__hash__":1258},"content\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis\u002Findex.md","uv Workspaces for Multi-Package Python CLIs",{"type":7,"value":8,"toc":1224},"minimark",[9,29,34,48,52,56,80,84,87,97,101,107,276,283,465,604,627,631,712,722,725,730,752,756,759,798,821,825,828,895,902,906,909,955,959,966,1113,1123,1127,1136,1140,1144,1151,1155,1162,1166,1173,1177,1184,1188,1220],[10,11,12,13,17,18,22,23,28],"p",{},"A CLI that grows successful often stops being one package. Another team wants to import its core logic without installing a command-line tool. Optional backends — AWS, GCP, a proprietary system — should be installable separately, so most users do not pull in huge SDKs. Plugins written in-house should live beside the tool and be tested against it on every change. You could split these into separate repositories and coordinate versions across them, or keep everything in one package and accept the dependency bloat. A ",[14,15,16],"strong",{},"uv workspace"," is the middle path: several packages in one repository, each with its own ",[19,20,21],"code",{},"pyproject.toml"," and each built and published independently, sharing a single lockfile and a single development environment. This guide sets up a workspace for a CLI, its core library and a plugin, covers everyday commands, building and publishing individual members, and CI. It belongs to the ",[24,25,27],"a",{"href":26},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002F","uv for Python CLI dependency management topic",".",[30,31,33],"h2",{"id":32},"prerequisites","Prerequisites",[35,36,37,45],"ul",{},[38,39,40,41,28],"li",{},"uv 0.5 or newer, and familiarity with a single-package uv project as in ",[24,42,44],{"href":43},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-init-vs-poetry-init-for-cli-tools\u002F","uv init vs Poetry init for CLI tools",[38,46,47],{},"A genuine reason to have more than one distributable package — see the decision below.",[30,49,51],{"id":50},"do-you-need-a-workspace","Do you need a workspace?",[53,54],"inline-diagram",{"name":55},"ws-when",[10,57,58,59,62,63,66,67,70,71,75,76,79],{},"Workspaces solve a ",[14,60,61],{},"release"," problem: several things that are installed or published separately but developed together. If your only goal is organising code, subpackages inside one distribution (",[19,64,65],{},"mytool.core",", ",[19,68,69],{},"mytool.cli",") do the job with less machinery, and ",[24,72,74],{"href":73},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fenforcing-import-boundaries-in-a-cli-codebase\u002F","import contracts"," can keep them separate. Reach for a workspace when someone outside the CLI needs to ",[19,77,78],{},"pip install mytool-core",", or when optional backends should be separate packages rather than extras.",[30,81,83],{"id":82},"the-layout","The layout",[53,85],{"name":86},"ws-tree",[88,89,95],"pre",{"className":90,"code":92,"language":93,"meta":94},[91],"language-text","repo\u002F\n├── pyproject.toml              # workspace root (not published)\n├── uv.lock                     # one lockfile for everything\n└── packages\u002F\n    ├── mytool-core\u002F\n    │   ├── pyproject.toml\n    │   └── src\u002Fmytool_core\u002F...\n    ├── mytool-cli\u002F\n    │   ├── pyproject.toml\n    │   └── src\u002Fmytool_cli\u002F...\n    └── mytool-aws\u002F\n        ├── pyproject.toml\n        └── src\u002Fmytool_aws\u002F...\n","text","",[19,96,92],{"__ignoreMap":94},[30,98,100],{"id":99},"the-recipe","The recipe",[10,102,103,104,106],{},"The root ",[19,105,21],{}," declares the workspace and holds shared development tooling. It is not itself a published package:",[88,108,112],{"className":109,"code":110,"language":111,"meta":94,"style":94},"language-toml shiki shiki-themes github-light github-dark","# pyproject.toml (root)\n[project]\nname = \"mytool-workspace\"\nversion = \"0\"\nrequires-python = \">=3.10\"\ndependencies = []\n\n[tool.uv.workspace]\nmembers = [\"packages\u002F*\"]\n\n[dependency-groups]\ndev = [\"pytest>=8\", \"ruff>=0.6\", \"mypy>=1.10\"]\n\n[tool.uv]\npackage = false          # the root is a workspace container, not a distribution\n","toml",[19,113,114,123,137,147,156,165,171,178,198,209,214,224,245,250,263],{"__ignoreMap":94},[115,116,119],"span",{"class":117,"line":118},"line",1,[115,120,122],{"class":121},"sJ8bj","# pyproject.toml (root)\n",[115,124,126,130,134],{"class":117,"line":125},2,[115,127,129],{"class":128},"sVt8B","[",[115,131,133],{"class":132},"sScJk","project",[115,135,136],{"class":128},"]\n",[115,138,140,143],{"class":117,"line":139},3,[115,141,142],{"class":128},"name = ",[115,144,146],{"class":145},"sZZnC","\"mytool-workspace\"\n",[115,148,150,153],{"class":117,"line":149},4,[115,151,152],{"class":128},"version = ",[115,154,155],{"class":145},"\"0\"\n",[115,157,159,162],{"class":117,"line":158},5,[115,160,161],{"class":128},"requires-python = ",[115,163,164],{"class":145},"\">=3.10\"\n",[115,166,168],{"class":117,"line":167},6,[115,169,170],{"class":128},"dependencies = []\n",[115,172,174],{"class":117,"line":173},7,[115,175,177],{"emptyLinePlaceholder":176},true,"\n",[115,179,181,183,186,188,191,193,196],{"class":117,"line":180},8,[115,182,129],{"class":128},[115,184,185],{"class":132},"tool",[115,187,28],{"class":128},[115,189,190],{"class":132},"uv",[115,192,28],{"class":128},[115,194,195],{"class":132},"workspace",[115,197,136],{"class":128},[115,199,201,204,207],{"class":117,"line":200},9,[115,202,203],{"class":128},"members = [",[115,205,206],{"class":145},"\"packages\u002F*\"",[115,208,136],{"class":128},[115,210,212],{"class":117,"line":211},10,[115,213,177],{"emptyLinePlaceholder":176},[115,215,217,219,222],{"class":117,"line":216},11,[115,218,129],{"class":128},[115,220,221],{"class":132},"dependency-groups",[115,223,136],{"class":128},[115,225,227,230,233,235,238,240,243],{"class":117,"line":226},12,[115,228,229],{"class":128},"dev = [",[115,231,232],{"class":145},"\"pytest>=8\"",[115,234,66],{"class":128},[115,236,237],{"class":145},"\"ruff>=0.6\"",[115,239,66],{"class":128},[115,241,242],{"class":145},"\"mypy>=1.10\"",[115,244,136],{"class":128},[115,246,248],{"class":117,"line":247},13,[115,249,177],{"emptyLinePlaceholder":176},[115,251,253,255,257,259,261],{"class":117,"line":252},14,[115,254,129],{"class":128},[115,256,185],{"class":132},[115,258,28],{"class":128},[115,260,190],{"class":132},[115,262,136],{"class":128},[115,264,266,269,273],{"class":117,"line":265},15,[115,267,268],{"class":128},"package = ",[115,270,272],{"class":271},"sj4cs","false",[115,274,275],{"class":121},"          # the root is a workspace container, not a distribution\n",[10,277,278,279,282],{},"Each member is a normal package. The CLI depends on the core library by name, and a ",[19,280,281],{},"[tool.uv.sources]"," entry tells uv to satisfy that dependency from the workspace rather than from PyPI:",[88,284,286],{"className":109,"code":285,"language":111,"meta":94,"style":94},"# packages\u002Fmytool-cli\u002Fpyproject.toml\n[project]\nname = \"mytool-cli\"\nversion = \"2.1.0\"\nrequires-python = \">=3.10\"\ndependencies = [\"mytool-core>=2.1,\u003C3\", \"typer>=0.12\"]\n\n[project.optional-dependencies]\naws = [\"mytool-aws>=2.1\"]\n\n[project.scripts]\nmytool = \"mytool_cli.app:app\"\n\n[tool.uv.sources]\nmytool-core = { workspace = true }\nmytool-aws = { workspace = true }\n\n[build-system]\nrequires = [\"uv_build>=0.8,\u003C0.12\"]\nbuild-backend = \"uv_build\"\n",[19,287,288,293,301,308,315,321,336,340,353,363,367,380,388,392,409,420,430,435,445,456],{"__ignoreMap":94},[115,289,290],{"class":117,"line":118},[115,291,292],{"class":121},"# packages\u002Fmytool-cli\u002Fpyproject.toml\n",[115,294,295,297,299],{"class":117,"line":125},[115,296,129],{"class":128},[115,298,133],{"class":132},[115,300,136],{"class":128},[115,302,303,305],{"class":117,"line":139},[115,304,142],{"class":128},[115,306,307],{"class":145},"\"mytool-cli\"\n",[115,309,310,312],{"class":117,"line":149},[115,311,152],{"class":128},[115,313,314],{"class":145},"\"2.1.0\"\n",[115,316,317,319],{"class":117,"line":158},[115,318,161],{"class":128},[115,320,164],{"class":145},[115,322,323,326,329,331,334],{"class":117,"line":167},[115,324,325],{"class":128},"dependencies = [",[115,327,328],{"class":145},"\"mytool-core>=2.1,\u003C3\"",[115,330,66],{"class":128},[115,332,333],{"class":145},"\"typer>=0.12\"",[115,335,136],{"class":128},[115,337,338],{"class":117,"line":173},[115,339,177],{"emptyLinePlaceholder":176},[115,341,342,344,346,348,351],{"class":117,"line":180},[115,343,129],{"class":128},[115,345,133],{"class":132},[115,347,28],{"class":128},[115,349,350],{"class":132},"optional-dependencies",[115,352,136],{"class":128},[115,354,355,358,361],{"class":117,"line":200},[115,356,357],{"class":128},"aws = [",[115,359,360],{"class":145},"\"mytool-aws>=2.1\"",[115,362,136],{"class":128},[115,364,365],{"class":117,"line":211},[115,366,177],{"emptyLinePlaceholder":176},[115,368,369,371,373,375,378],{"class":117,"line":216},[115,370,129],{"class":128},[115,372,133],{"class":132},[115,374,28],{"class":128},[115,376,377],{"class":132},"scripts",[115,379,136],{"class":128},[115,381,382,385],{"class":117,"line":226},[115,383,384],{"class":128},"mytool = ",[115,386,387],{"class":145},"\"mytool_cli.app:app\"\n",[115,389,390],{"class":117,"line":247},[115,391,177],{"emptyLinePlaceholder":176},[115,393,394,396,398,400,402,404,407],{"class":117,"line":252},[115,395,129],{"class":128},[115,397,185],{"class":132},[115,399,28],{"class":128},[115,401,190],{"class":132},[115,403,28],{"class":128},[115,405,406],{"class":132},"sources",[115,408,136],{"class":128},[115,410,411,414,417],{"class":117,"line":265},[115,412,413],{"class":128},"mytool-core = { workspace = ",[115,415,416],{"class":271},"true",[115,418,419],{"class":128}," }\n",[115,421,423,426,428],{"class":117,"line":422},16,[115,424,425],{"class":128},"mytool-aws = { workspace = ",[115,427,416],{"class":271},[115,429,419],{"class":128},[115,431,433],{"class":117,"line":432},17,[115,434,177],{"emptyLinePlaceholder":176},[115,436,438,440,443],{"class":117,"line":437},18,[115,439,129],{"class":128},[115,441,442],{"class":132},"build-system",[115,444,136],{"class":128},[115,446,448,451,454],{"class":117,"line":447},19,[115,449,450],{"class":128},"requires = [",[115,452,453],{"class":145},"\"uv_build>=0.8,\u003C0.12\"",[115,455,136],{"class":128},[115,457,459,462],{"class":117,"line":458},20,[115,460,461],{"class":128},"build-backend = ",[115,463,464],{"class":145},"\"uv_build\"\n",[88,466,468],{"className":109,"code":467,"language":111,"meta":94,"style":94},"# packages\u002Fmytool-aws\u002Fpyproject.toml\n[project]\nname = \"mytool-aws\"\nversion = \"2.1.0\"\nrequires-python = \">=3.10\"\ndependencies = [\"mytool-core>=2.1,\u003C3\", \"boto3>=1.34\"]\n\n[project.entry-points.\"mytool.backends\"]\naws = \"mytool_aws:AwsBackend\"\n\n[tool.uv.sources]\nmytool-core = { workspace = true }\n\n[build-system]\nrequires = [\"uv_build>=0.8,\u003C0.12\"]\nbuild-backend = \"uv_build\"\n",[19,469,470,475,483,490,496,502,515,519,542,550,554,570,578,582,590,598],{"__ignoreMap":94},[115,471,472],{"class":117,"line":118},[115,473,474],{"class":121},"# packages\u002Fmytool-aws\u002Fpyproject.toml\n",[115,476,477,479,481],{"class":117,"line":125},[115,478,129],{"class":128},[115,480,133],{"class":132},[115,482,136],{"class":128},[115,484,485,487],{"class":117,"line":139},[115,486,142],{"class":128},[115,488,489],{"class":145},"\"mytool-aws\"\n",[115,491,492,494],{"class":117,"line":149},[115,493,152],{"class":128},[115,495,314],{"class":145},[115,497,498,500],{"class":117,"line":158},[115,499,161],{"class":128},[115,501,164],{"class":145},[115,503,504,506,508,510,513],{"class":117,"line":167},[115,505,325],{"class":128},[115,507,328],{"class":145},[115,509,66],{"class":128},[115,511,512],{"class":145},"\"boto3>=1.34\"",[115,514,136],{"class":128},[115,516,517],{"class":117,"line":173},[115,518,177],{"emptyLinePlaceholder":176},[115,520,521,523,525,527,530,532,535,537,540],{"class":117,"line":180},[115,522,129],{"class":128},[115,524,133],{"class":132},[115,526,28],{"class":128},[115,528,529],{"class":132},"entry-points",[115,531,28],{"class":128},[115,533,534],{"class":132},"\"mytool",[115,536,28],{"class":128},[115,538,539],{"class":132},"backends\"",[115,541,136],{"class":128},[115,543,544,547],{"class":117,"line":200},[115,545,546],{"class":128},"aws = ",[115,548,549],{"class":145},"\"mytool_aws:AwsBackend\"\n",[115,551,552],{"class":117,"line":211},[115,553,177],{"emptyLinePlaceholder":176},[115,555,556,558,560,562,564,566,568],{"class":117,"line":216},[115,557,129],{"class":128},[115,559,185],{"class":132},[115,561,28],{"class":128},[115,563,190],{"class":132},[115,565,28],{"class":128},[115,567,406],{"class":132},[115,569,136],{"class":128},[115,571,572,574,576],{"class":117,"line":226},[115,573,413],{"class":128},[115,575,416],{"class":271},[115,577,419],{"class":128},[115,579,580],{"class":117,"line":247},[115,581,177],{"emptyLinePlaceholder":176},[115,583,584,586,588],{"class":117,"line":252},[115,585,129],{"class":128},[115,587,442],{"class":132},[115,589,136],{"class":128},[115,591,592,594,596],{"class":117,"line":265},[115,593,450],{"class":128},[115,595,453],{"class":145},[115,597,136],{"class":128},[115,599,600,602],{"class":117,"line":422},[115,601,461],{"class":128},[115,603,464],{"class":145},[10,605,606,607,610,611,614,615,618,619,622,623,28],{},"The key idea is that ",[14,608,609],{},"the published metadata is ordinary",": ",[19,612,613],{},"mytool-cli"," declares a normal dependency on ",[19,616,617],{},"mytool-core>=2.1,\u003C3",", which is what users' installers will resolve from PyPI. The ",[19,620,621],{},"workspace = true"," source only affects development inside this repository, where uv installs the local copy in editable mode. The plugin announces itself through an entry point, so the CLI discovers it at runtime when installed — the mechanism described in ",[24,624,626],{"href":625},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fdiscovering-plugins-with-entry-points\u002F","discovering plugins with entry points",[30,628,630],{"id":629},"everyday-commands","Everyday commands",[88,632,636],{"className":633,"code":634,"language":635,"meta":94,"style":94},"language-bash shiki shiki-themes github-light github-dark","uv sync --all-packages                 # one .venv with every member installed (editable)\nuv run --package mytool-cli mytool --help\nuv run --package mytool-core pytest packages\u002Fmytool-core\nuv add --package mytool-aws \"boto3>=1.35\"\nuv lock                                # re-resolve the whole workspace\n","bash",[19,637,638,651,670,687,702],{"__ignoreMap":94},[115,639,640,642,645,648],{"class":117,"line":118},[115,641,190],{"class":132},[115,643,644],{"class":145}," sync",[115,646,647],{"class":271}," --all-packages",[115,649,650],{"class":121},"                 # one .venv with every member installed (editable)\n",[115,652,653,655,658,661,664,667],{"class":117,"line":125},[115,654,190],{"class":132},[115,656,657],{"class":145}," run",[115,659,660],{"class":271}," --package",[115,662,663],{"class":145}," mytool-cli",[115,665,666],{"class":145}," mytool",[115,668,669],{"class":271}," --help\n",[115,671,672,674,676,678,681,684],{"class":117,"line":139},[115,673,190],{"class":132},[115,675,657],{"class":145},[115,677,660],{"class":271},[115,679,680],{"class":145}," mytool-core",[115,682,683],{"class":145}," pytest",[115,685,686],{"class":145}," packages\u002Fmytool-core\n",[115,688,689,691,694,696,699],{"class":117,"line":149},[115,690,190],{"class":132},[115,692,693],{"class":145}," add",[115,695,660],{"class":271},[115,697,698],{"class":145}," mytool-aws",[115,700,701],{"class":145}," \"boto3>=1.35\"\n",[115,703,704,706,709],{"class":117,"line":158},[115,705,190],{"class":132},[115,707,708],{"class":145}," lock",[115,710,711],{"class":121},"                                # re-resolve the whole workspace\n",[10,713,714,717,718,721],{},[19,715,716],{},"--package"," selects which member a command applies to; without it, uv uses the member whose directory you are in (or the root). ",[19,719,720],{},"uv sync --all-packages"," gives developers one environment where the CLI, core and plugin are all installed from the working tree, so a change in core is immediately visible when running the CLI.",[53,723],{"name":724},"ws-terminal",[726,727,729],"h3",{"id":728},"one-lockfile-consistent-versions","One lockfile, consistent versions",[10,731,732,733,736,737,740,741,744,745,747,748,751],{},"The single ",[19,734,735],{},"uv.lock"," means every member is developed and tested against exactly the same versions of shared dependencies — there is no way for ",[19,738,739],{},"mytool-core"," to be tested with ",[19,742,743],{},"pydantic"," 2.8 while ",[19,746,613],{}," uses 2.10. That consistency is the main technical benefit over separate repositories, and it makes CI simpler: one ",[19,749,750],{},"uv sync --locked",", one cache key.",[30,753,755],{"id":754},"building-and-publishing-members","Building and publishing members",[10,757,758],{},"Each member builds to its own wheel and sdist:",[88,760,762],{"className":633,"code":761,"language":635,"meta":94,"style":94},"uv build --package mytool-core\nuv build --package mytool-cli\nuv build --all-packages                # everything, into dist\u002F\n",[19,763,764,776,787],{"__ignoreMap":94},[115,765,766,768,771,773],{"class":117,"line":118},[115,767,190],{"class":132},[115,769,770],{"class":145}," build",[115,772,660],{"class":271},[115,774,775],{"class":145}," mytool-core\n",[115,777,778,780,782,784],{"class":117,"line":125},[115,779,190],{"class":132},[115,781,770],{"class":145},[115,783,660],{"class":271},[115,785,786],{"class":145}," mytool-cli\n",[115,788,789,791,793,795],{"class":117,"line":139},[115,790,190],{"class":132},[115,792,770],{"class":145},[115,794,647],{"class":271},[115,796,797],{"class":121},"                # everything, into dist\u002F\n",[10,799,800,801,804,805,808,809,812,813,816,817,28],{},"For releases, the simplest policy is ",[14,802,803],{},"lockstep versioning",": all members share a version and are released together from one tag. It makes compatibility obvious (",[19,806,807],{},"mytool-cli 2.1.0"," works with ",[19,810,811],{},"mytool-core 2.1.0",") and the constraints easy to write. Independent versioning is possible — per-package tags such as ",[19,814,815],{},"core-v2.1.0"," — but every inter-package constraint then needs thought. Publishing works exactly as for a single package, with trusted publishing configured once per PyPI project; see ",[24,818,820],{"href":819},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fpublishing-to-pypi-with-trusted-publishing\u002F","publishing to PyPI with trusted publishing",[30,822,824],{"id":823},"moving-an-existing-cli-into-a-workspace","Moving an existing CLI into a workspace",[10,826,827],{},"Most workspaces start as a single package that outgrew itself. The move can be done in small, reviewable steps without breaking users:",[829,830,831,851,864,878],"ol",{},[38,832,833,839,840,842,843,846,847,850],{},[14,834,835,836,28],{},"Create the root and move the existing package under ",[19,837,838],{},"packages\u002F"," Keep its distribution name and version unchanged, add the root ",[19,841,21],{}," with ",[19,844,845],{},"[tool.uv.workspace]",", run ",[19,848,849],{},"uv lock",", and confirm tests pass. Users see no difference — the published package is identical.",[38,852,853,856,857,859,860,863],{},[14,854,855],{},"Extract the core library."," Move modules with no CLI dependencies into a new ",[19,858,739],{}," member, and have the CLI depend on it with a workspace source. Keep thin re-export shims in the old import paths for a release or two so any external code importing ",[19,861,862],{},"mytool.models"," keeps working, with a deprecation warning.",[38,865,866,869,870,873,874,877],{},[14,867,868],{},"Split optional backends last."," Turn a heavy extra into its own member only when there is a clear benefit — independent release cadence, or a dependency so large it deserves a separate install. Keep the extra on the CLI (",[19,871,872],{},"mytool-cli[aws]"," depending on ",[19,875,876],{},"mytool-aws",") so existing install commands continue to work.",[38,879,880,883,884,886,887,890,891,894],{},[14,881,882],{},"Publish the new packages before the CLI depends on them."," A release of ",[19,885,613],{}," that requires ",[19,888,889],{},"mytool-core>=2.1"," must not reach PyPI before ",[19,892,893],{},"mytool-core 2.1"," does; lockstep releases from one tag, publishing members in dependency order, handle this naturally.",[10,896,897,898,901],{},"Each step is a normal pull request with CI green, and at no point does a user's ",[19,899,900],{},"pipx upgrade"," break.",[30,903,905],{"id":904},"ux-considerations","UX considerations",[10,907,908],{},"The users of a workspace layout are both end users and contributors:",[35,910,911,925,934,949],{},[38,912,913,916,917,920,921,924],{},[14,914,915],{},"End users should not notice it."," ",[19,918,919],{},"pipx install mytool-cli"," (or ",[19,922,923],{},"\"mytool-cli[aws]\"",") must work exactly as for a single package. Test that by installing the built wheels into a clean environment, not from the workspace.",[38,926,927,930,931,933],{},[14,928,929],{},"Contributors need one command to get going."," Document ",[19,932,720],{}," as the setup step; everything else follows.",[38,935,936,916,939,66,941,66,943,945,946,28],{},[14,937,938],{},"Keep member names parallel.",[19,940,739],{},[19,942,613],{},[19,944,876],{}," makes the family obvious on PyPI and in ",[19,947,948],{},"pip list",[38,950,951,954],{},[14,952,953],{},"Put the command in the CLI package only."," A core library that installs a console script surprises people who only wanted the library.",[30,956,958],{"id":957},"testing-the-behaviour","Testing the behaviour",[10,960,961,962,965],{},"Test each member in isolation as well as together. The workspace environment has everything installed, which can hide a missing dependency declaration — core code that accidentally imports ",[19,963,964],{},"typer",", available only because the CLI member depends on it. Run each member's tests in an environment containing only that member:",[88,967,971],{"className":968,"code":969,"language":970,"meta":94,"style":94},"language-yaml shiki shiki-themes github-light github-dark","# .github\u002Fworkflows\u002Fci.yml (excerpt)\n  test:\n    strategy:\n      matrix:\n        package: [mytool-core, mytool-cli, mytool-aws]\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: astral-sh\u002Fsetup-uv@v6\n        with:\n          enable-cache: true\n          cache-dependency-glob: |\n            uv.lock\n            packages\u002F*\u002Fpyproject.toml\n      - run: uv sync --locked --package ${{ matrix.package }} --group dev\n      - run: uv run --package ${{ matrix.package }} pytest packages\u002F${{ matrix.package }}\n","yaml",[19,972,973,978,987,994,1001,1021,1028,1041,1052,1059,1069,1080,1085,1090,1102],{"__ignoreMap":94},[115,974,975],{"class":117,"line":118},[115,976,977],{"class":121},"# .github\u002Fworkflows\u002Fci.yml (excerpt)\n",[115,979,980,984],{"class":117,"line":125},[115,981,983],{"class":982},"s9eBZ","  test",[115,985,986],{"class":128},":\n",[115,988,989,992],{"class":117,"line":139},[115,990,991],{"class":982},"    strategy",[115,993,986],{"class":128},[115,995,996,999],{"class":117,"line":149},[115,997,998],{"class":982},"      matrix",[115,1000,986],{"class":128},[115,1002,1003,1006,1009,1011,1013,1015,1017,1019],{"class":117,"line":158},[115,1004,1005],{"class":982},"        package",[115,1007,1008],{"class":128},": [",[115,1010,739],{"class":145},[115,1012,66],{"class":128},[115,1014,613],{"class":145},[115,1016,66],{"class":128},[115,1018,876],{"class":145},[115,1020,136],{"class":128},[115,1022,1023,1026],{"class":117,"line":167},[115,1024,1025],{"class":982},"    steps",[115,1027,986],{"class":128},[115,1029,1030,1033,1036,1038],{"class":117,"line":173},[115,1031,1032],{"class":128},"      - ",[115,1034,1035],{"class":982},"uses",[115,1037,610],{"class":128},[115,1039,1040],{"class":145},"actions\u002Fcheckout@v4\n",[115,1042,1043,1045,1047,1049],{"class":117,"line":180},[115,1044,1032],{"class":128},[115,1046,1035],{"class":982},[115,1048,610],{"class":128},[115,1050,1051],{"class":145},"astral-sh\u002Fsetup-uv@v6\n",[115,1053,1054,1057],{"class":117,"line":200},[115,1055,1056],{"class":982},"        with",[115,1058,986],{"class":128},[115,1060,1061,1064,1066],{"class":117,"line":211},[115,1062,1063],{"class":982},"          enable-cache",[115,1065,610],{"class":128},[115,1067,1068],{"class":271},"true\n",[115,1070,1071,1074,1076],{"class":117,"line":216},[115,1072,1073],{"class":982},"          cache-dependency-glob",[115,1075,610],{"class":128},[115,1077,1079],{"class":1078},"szBVR","|\n",[115,1081,1082],{"class":117,"line":226},[115,1083,1084],{"class":145},"            uv.lock\n",[115,1086,1087],{"class":117,"line":247},[115,1088,1089],{"class":145},"            packages\u002F*\u002Fpyproject.toml\n",[115,1091,1092,1094,1097,1099],{"class":117,"line":252},[115,1093,1032],{"class":128},[115,1095,1096],{"class":982},"run",[115,1098,610],{"class":128},[115,1100,1101],{"class":145},"uv sync --locked --package ${{ matrix.package }} --group dev\n",[115,1103,1104,1106,1108,1110],{"class":117,"line":265},[115,1105,1032],{"class":128},[115,1107,1096],{"class":982},[115,1109,610],{"class":128},[115,1111,1112],{"class":145},"uv run --package ${{ matrix.package }} pytest packages\u002F${{ matrix.package }}\n",[10,1114,1115,1118,1119,28],{},[19,1116,1117],{},"uv sync --package X"," installs only that member and its declared dependencies, so an undeclared import fails the job. Add one job that installs the built wheels together and runs the CLI's smoke test, proving the published packages fit together exactly as they will for users. The cache settings are explained in ",[24,1120,1122],{"href":1121},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fcaching-uv-dependencies-in-ci\u002F","caching uv dependencies in CI",[30,1124,1126],{"id":1125},"conclusion","Conclusion",[10,1128,1129,1130,1132,1133,1135],{},"A uv workspace keeps a family of packages — a CLI, its core library, optional backends and plugins — in one repository with one lockfile, while each remains an ordinary, independently installable distribution. Declare members in the root, connect them with ",[19,1131,621],{}," sources over normal published constraints, use ",[19,1134,716],{}," for everyday commands, version in lockstep unless you have a reason not to, and test each member alone so undeclared dependencies cannot hide. Use it when parts are released separately; otherwise, subpackages are simpler.",[30,1137,1139],{"id":1138},"frequently-asked-questions","Frequently asked questions",[726,1141,1143],{"id":1142},"can-members-require-different-python-versions","Can members require different Python versions?",[10,1145,1146,1147,1150],{},"The workspace resolves a single lockfile for the intersection of all members' ",[19,1148,1149],{},"requires-python"," ranges, so the effective range is the narrowest. Members that genuinely need different Python versions belong in separate projects.",[726,1152,1154],{"id":1153},"how-is-a-workspace-different-from-path-dependencies","How is a workspace different from path dependencies?",[10,1156,1157,1158,1161],{},"Path dependencies (",[19,1159,1160],{},"{ path = \"..\u002Fcore\" }",") link separate projects, each with its own lockfile. A workspace shares one lockfile and environment. Use path dependencies for loosely related projects; use a workspace for a family released together.",[726,1163,1165],{"id":1164},"can-a-member-depend-on-another-members-extra","Can a member depend on another member's extra?",[10,1167,1168,1169,1172],{},"Yes, with standard syntax: ",[19,1170,1171],{},"dependencies = [\"mytool-core[yaml]>=2.1\"]",", plus the workspace source. uv resolves the extra from the workspace member.",[726,1174,1176],{"id":1175},"how-do-i-stop-the-root-from-being-built-or-published","How do I stop the root from being built or published?",[10,1178,1179,1180,1183],{},"Set ",[19,1181,1182],{},"[tool.uv] package = false"," in the root, as shown, and omit a build system there. uv then treats the root purely as a workspace container.",[30,1185,1187],{"id":1186},"related","Related",[35,1189,1190,1196,1202,1208,1214],{},[38,1191,1192,1193],{},"Up: ",[24,1194,1195],{"href":26},"uv for Python CLI dependency management",[38,1197,1198],{},[24,1199,1201],{"href":1200},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Frunning-one-off-cli-scripts-with-uv-run\u002F","Running one-off CLI scripts with uv run",[38,1203,1204],{},[24,1205,1207],{"href":1206},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-tool-install-vs-pipx-for-clis\u002F","uv tool install vs pipx for CLIs",[38,1209,1210],{},[24,1211,1213],{"href":1212},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002F","Plugin architectures for extensible CLIs",[38,1215,1216],{},[24,1217,1219],{"href":1218},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fmigrating-a-cli-from-poetry-to-uv\u002F","Migrating a CLI from Poetry to uv",[1221,1222,1223],"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 .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}",{"title":94,"searchDepth":125,"depth":125,"links":1225},[1226,1227,1228,1229,1230,1233,1234,1235,1236,1237,1238,1244],{"id":32,"depth":125,"text":33},{"id":50,"depth":125,"text":51},{"id":82,"depth":125,"text":83},{"id":99,"depth":125,"text":100},{"id":629,"depth":125,"text":630,"children":1231},[1232],{"id":728,"depth":139,"text":729},{"id":754,"depth":125,"text":755},{"id":823,"depth":125,"text":824},{"id":904,"depth":125,"text":905},{"id":957,"depth":125,"text":958},{"id":1125,"depth":125,"text":1126},{"id":1138,"depth":125,"text":1139,"children":1239},[1240,1241,1242,1243],{"id":1142,"depth":139,"text":1143},{"id":1153,"depth":139,"text":1154},{"id":1164,"depth":139,"text":1165},{"id":1175,"depth":139,"text":1176},{"id":1186,"depth":125,"text":1187},"2026-09-18","Split a Python CLI into a core library, the command package and plugins in one uv workspace: one lockfile, workspace sources, per-package runs, builds and CI.","advanced",false,"md",{},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis",{"title":5,"description":1246},"project-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis\u002Findex",[190,1255,1256,1257],"workspaces","monorepo","packaging","xyJYLWcXCHxmCf4_GoYrZR7V4JgcLYtYQnc-fbhUQiY",[1260,1263,1266,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,1728,1731,1734,1737,1740,1743,1746,1749,1752,1755,1758,1761,1764,1767,1770,1773,1776,1779,1782,1785,1788,1791,1794,1797,1800,1803,1806,1809,1812,1815,1818,1821,1824,1827,1830,1833,1836,1839,1842,1845,1848,1851,1854,1857,1860,1863,1866,1869,1872,1875,1878,1881,1884,1887,1890,1893,1896,1899,1902,1905,1908,1911,1914,1917,1920,1923,1926,1929,1932,1935,1938,1941,1944,1947,1950,1953,1956,1959,1962,1965,1968,1971,1974,1977,1980,1983,1986,1989,1992,1995,1998,2001,2004,2007,2010,2013,2016,2019,2022,2025,2028,2031,2034,2037,2040,2043,2046,2049,2052,2055,2058,2061,2064,2067,2070,2073,2076,2079,2081,2082,2085,2088,2091,2094,2097,2100],{"path":1261,"title":1262},"\u002Fabout","About Python CLI Toolcraft",{"path":1264,"title":1265},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies","Advanced Argument Validation Strategies",{"path":1267,"title":1268},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fparsing-nested-json-arguments-in-python-clis","Parsing Nested JSON Args in Python CLIs",{"path":1270,"title":1271},"\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":1273,"title":1274},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-dependent-and-conflicting-options","Validating Dependent and Conflicting CLI Options",{"path":1276,"title":1277},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-file-and-directory-paths-in-clis","Validating File and Directory Paths in CLIs",{"path":1279,"title":1280},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-urls-hosts-and-ports","Validating URLs, Hosts and Ports in Python CLI Arguments",{"path":1282,"title":1283},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fwriting-custom-click-parameter-types","Writing Custom Click Parameter Types",{"path":1285,"title":1286},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fbrowsing-records-with-a-textual-datatable","Browsing Records with a Textual DataTable Picker",{"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\u002Frunning-background-work-in-textual-with-workers","Running Background Work in Textual with Workers",{"path":1300,"title":1301},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fstyling-textual-apps-with-tcss","Styling Textual Apps with TCSS",{"path":1303,"title":1304},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Ftesting-textual-apps-with-pilot","Testing Textual Apps with Pilot",{"path":1306,"title":1307},"\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":1309,"title":1310},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fdocumenting-environment-variables-in-help","Documenting Environment Variables in CLI Help",{"path":1312,"title":1313},"\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":1315,"title":1316},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation","CLI Help Output and Documentation",{"path":1318,"title":1319},"\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":1321,"title":1322},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fversioning-and-deprecating-cli-flags","Versioning and Deprecating CLI Flags",{"path":1324,"title":1325},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fwriting-help-text-users-actually-read","Writing Help Text Users Actually Read",{"path":1327,"title":1328},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fadapting-output-to-terminal-width","Adapting Python CLI Output to Terminal Width",{"path":1330,"title":1331},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fdetecting-ci-environments-and-non-interactive-shells","Detecting CI Environments and Non-Interactive Shells",{"path":1333,"title":1334},"\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":1336,"title":1337},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fhandling-ansi-escape-codes-on-windows-consoles","Handling ANSI Escape Codes on Windows Consoles",{"path":1339,"title":1340},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility","Cross-Platform Terminal Compatibility for Python CLIs",{"path":1342,"title":1343},"\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":1345,"title":1346},"\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":1348,"title":1349},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fchoosing-exit-codes-for-cli-tools","Choosing Exit Codes for CLI Tools",{"path":1351,"title":1352},"\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":1354,"title":1355},"\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":1357,"title":1358},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Ffriendly-error-messages-and-tracebacks","Friendly Error Messages and Tracebacks",{"path":1360,"title":1361},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fhandling-keyboard-interrupt-cleanly","Handling Keyboard Interrupt Cleanly",{"path":1363,"title":1364},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes","Error Handling and Exit Codes for CLIs",{"path":1366,"title":1367},"\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":1369,"title":1370},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fwriting-crash-reports-users-can-send","Writing Crash Reports Users Can Send",{"path":1372,"title":1373},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Fconfig-precedence-flags-env-files-defaults","Config Precedence: Flags, Env, Files, Defaults",{"path":1375,"title":1376},"\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":1378,"title":1379},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars","Handling Config Files and Env Vars in CLIs",{"path":1381,"title":1382},"\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":1384,"title":1385},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Freading-toml-config-with-tomllib","Reading TOML Config with tomllib in Python CLIs",{"path":1387,"title":1388},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Ftyped-settings-with-pydantic-settings","Typed Settings with pydantic-settings in Python CLIs",{"path":1390,"title":1391},"\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":1393,"title":1394},"\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":1396,"title":1397},"\u002Fadvanced-input-parsing-user-experience","Advanced Input Parsing for Python CLIs",{"path":1399,"title":1400},"\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":1402,"title":1403},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Fbuilding-interactive-prompts-and-menus","Building Interactive Prompts and Menus in Python CLIs",{"path":1405,"title":1406},"\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":1408,"title":1409},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich","Interactive Terminal UI with Rich",{"path":1411,"title":1412},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Flive-dashboards-with-rich-live","Live Dashboards with Rich Live in Python CLIs",{"path":1414,"title":1415},"\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":1417,"title":1418},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Frendering-tables-and-json-with-rich","Rendering Tables and JSON with Rich",{"path":1420,"title":1421},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Ftheming-rich-output-consistently","Theming Rich Output Consistently in Python CLIs",{"path":1423,"title":1424},"\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":1426,"title":1427},"\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":1429,"title":1430},"\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":1432,"title":1433},"\u002Fadvanced-input-parsing-user-experience\u002Foutput-formats-for-data-clis","Output Formats for Data-Heavy Python CLIs",{"path":1435,"title":1436},"\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":1438,"title":1439},"\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":1441,"title":1442},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fargcomplete-for-argparse-clis","Tab Completion for argparse CLIs with argcomplete",{"path":1444,"title":1445},"\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":1447,"title":1448},"\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":1450,"title":1451},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis","Shell Completion for Python CLIs",{"path":1453,"title":1454},"\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":1456,"title":1457},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fshipping-completion-scripts-with-packages","Shipping Shell Completion Scripts with a Python CLI",{"path":1459,"title":1460},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Ftesting-shell-completion-in-python-clis","Testing Shell Completion in Python CLIs",{"path":1462,"title":1463},"\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":1465,"title":1466},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fadding-verbose-and-quiet-logging-flags","Adding Verbose and Quiet Logging Flags",{"path":1468,"title":1469},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps","Structured Logging for CLI Apps",{"path":1471,"title":1472},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Flogging-with-structlog-in-a-cli","Logging with structlog in a Python CLI",{"path":1474,"title":1475},"\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":1477,"title":1478},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fstructured-json-logging-in-python-clis","Structured JSON Logging in Python CLIs",{"path":1480,"title":1481},"\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":1483,"title":1484},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fdetecting-tty-and-adapting-output","Detecting a TTY and Adapting Output",{"path":1486,"title":1487},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Femitting-json-output-for-scripting","Emitting JSON Output for Scripting",{"path":1489,"title":1490},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fhandling-broken-pipe-and-sigpipe","Handling Broken Pipe and SIGPIPE",{"path":1492,"title":1493},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes","Working with stdin, stdout and Pipes",{"path":1495,"title":1496},"\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":1498,"title":1499},"\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":1501,"title":1502},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Freading-piped-input-in-python-clis","Reading Piped Input in Python CLIs",{"path":1504,"title":1505},"\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":1507,"title":1508},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fdownloading-files-with-progress-in-python","Downloading Files with Progress in Python CLIs",{"path":1510,"title":1511},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis","Calling HTTP APIs from Python CLIs",{"path":1513,"title":1514},"\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":1516,"title":1517},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Foauth-device-flow-login-for-clis","OAuth Device Flow Login for Python CLIs",{"path":1519,"title":1520},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fpaginating-api-results-in-a-cli","Paginating API Results in a Python CLI",{"path":1522,"title":1523},"\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":1525,"title":1526},"\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":1528,"title":1529},"\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":1531,"title":1532},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis","Concurrency and Async in Python CLIs",{"path":1534,"title":1535},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fmultiprocessing-for-cpu-bound-cli-tasks","Multiprocessing for CPU-Bound CLI Tasks",{"path":1537,"title":1538},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fparallelising-cli-work-with-thread-pools","Parallelising CLI Work with Thread Pools",{"path":1540,"title":1541},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Frate-limiting-concurrent-requests-in-clis","Rate-Limiting Concurrent Requests in Python CLIs",{"path":1543,"title":1544},"\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":1546,"title":1547},"\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":1549,"title":1550},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fstructured-concurrency-with-taskgroups-in-clis","Structured Concurrency with TaskGroups in Python CLIs",{"path":1552,"title":1553},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fcross-platform-paths-with-pathlib","Cross-Platform Paths with pathlib in CLIs",{"path":1555,"title":1556},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Ffile-locking-for-concurrent-cli-runs","File Locking for Concurrent CLI Runs in Python",{"path":1558,"title":1559},"\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":1561,"title":1562},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes","Filesystem Paths and Atomic Writes for CLIs",{"path":1564,"title":1565},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fsafe-temporary-files-and-directories","Safe Temporary Files and Directories in CLIs",{"path":1567,"title":1568},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fstoring-app-data-with-platformdirs","Storing CLI App Data with platformdirs",{"path":1570,"title":1571},"\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":1573,"title":1574},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fwriting-files-atomically-in-python-clis","Writing Files Atomically in Python CLIs",{"path":1576,"title":1577},"\u002Fcli-runtime-systems-integration","CLI Runtime & Systems Integration for Python",{"path":1579,"title":1580},"\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":1582,"title":1583},"\u002Fcli-runtime-systems-integration\u002Flocal-state-and-sqlite-in-python-clis","Local State and SQLite in Python CLIs",{"path":1585,"title":1586},"\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":1588,"title":1589},"\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":1591,"title":1592},"\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":1594,"title":1595},"\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":1597,"title":1598},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fhandling-sigterm-and-graceful-shutdown","Handling SIGTERM and Graceful Shutdown in CLIs",{"path":1600,"title":1601},"\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":1603,"title":1604},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis","Long-Running and Watch-Mode Python CLIs",{"path":1606,"title":1607},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Freloading-config-on-sighup","Reloading Configuration on SIGHUP in a Python CLI",{"path":1609,"title":1610},"\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":1612,"title":1613},"\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":1615,"title":1616},"\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":1618,"title":1619},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Favoiding-shell-injection-in-python-clis","Avoiding Shell Injection in Python CLIs",{"path":1621,"title":1622},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fcalling-external-commands-safely-with-subprocess","Calling External Commands Safely with subprocess",{"path":1624,"title":1625},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fhandling-subprocess-timeouts-and-exit-codes","Handling Subprocess Timeouts and Exit Codes",{"path":1627,"title":1628},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis","Running Subprocesses from Python CLIs",{"path":1630,"title":1631},"\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":1633,"title":1634},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fpiping-between-subprocesses-in-python","Piping Between Subprocesses in Python Without a Shell",{"path":1636,"title":1637},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fstreaming-subprocess-output-in-real-time","Streaming Subprocess Output in Real Time",{"path":1639,"title":1640},"\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":1642,"title":1643},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis","Secrets and Credentials in Python CLIs",{"path":1645,"title":1646},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fprompting-for-passwords-securely","Prompting for Passwords Securely in Python CLIs",{"path":1648,"title":1649},"\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":1651,"title":1652},"\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":1654,"title":1655},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Frefreshing-expired-tokens-automatically","Refreshing Expired Tokens Automatically in a Python CLI",{"path":1657,"title":1658},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fstoring-tokens-with-keyring","Storing CLI Tokens Securely with keyring",{"path":1660,"title":1661},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fsupporting-multiple-profiles-and-accounts","Supporting Multiple Profiles and Accounts in CLIs",{"path":1663,"title":1664},"\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":1666,"title":1667},"\u002Fcli-runtime-systems-integration\u002Fupdate-checks-and-self-updating-clis","Update Checks, Upgrade Commands and Telemetry for Python CLIs",{"path":1669,"title":1670},"\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":1672,"title":1673},"\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":1675,"title":1676},"\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":1678,"title":1679},"\u002F","Python CLI Toolcraft",{"path":1681,"title":1682},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cleo","Building a Python CLI with Cleo Command Classes",{"path":1684,"title":1685},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cyclopts","Building a Type-Hinted Python CLI with Cyclopts",{"path":1687,"title":1688},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks","Beyond Click and Typer: Alternative Python CLI Frameworks",{"path":1690,"title":1691},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fquick-clis-from-functions-with-python-fire","Quick CLIs from Functions with Python Fire",{"path":1693,"title":1694},"\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":1696,"title":1697},"\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":1699,"title":1700},"\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":1702,"title":1703},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fguarding-startup-with-import-tests","Guarding CLI Startup with Import Tests",{"path":1705,"title":1706},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading","CLI Startup Performance and Lazy Loading",{"path":1708,"title":1709},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Flazy-loading-subcommands-for-faster-startup","Lazy Loading Subcommands for Faster Startup",{"path":1711,"title":1712},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fprofiling-python-cli-startup-time","Profiling Python CLI Startup Time",{"path":1714,"title":1715},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Freducing-cli-dependency-weight","Reducing CLI Dependency Weight",{"path":1717,"title":1718},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-subparsers-for-subcommands","argparse Subparsers for Subcommands",{"path":1720,"title":1721},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-vs-click-vs-typer-comparison","argparse vs Click vs Typer Compared",{"path":1723,"title":1724},"\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":1726,"title":1727},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse","Command-Line Parsing with argparse",{"path":1729,"title":1730},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmigrating-from-argparse-to-typer","Migrating from argparse to Typer",{"path":1732,"title":1733},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmutually-exclusive-options-in-argparse","Mutually Exclusive Options in argparse",{"path":1735,"title":1736},"\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":1738,"title":1739},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fwriting-custom-argparse-actions","Writing Custom argparse Actions in Python",{"path":1741,"title":1742},"\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":1744,"title":1745},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fdesigning-idempotent-commands","Designing Idempotent Commands in a Python CLI",{"path":1747,"title":1748},"\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":1750,"title":1751},"\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":1753,"title":1754},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions","Designing CLI Interfaces and Conventions in Python",{"path":1756,"title":1757},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fnaming-commands-and-flags-consistently","Naming Commands and Flags Consistently in Python CLIs",{"path":1759,"title":1760},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fpositional-arguments-vs-options","Positional Arguments vs Options: Designing a CLI Signature",{"path":1762,"title":1763},"\u002Fmodern-python-cli-frameworks-architecture","Python CLI Frameworks and Architecture",{"path":1765,"title":1766},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fdiscovering-plugins-with-entry-points","Discovering Plugins with Entry Points in Python CLIs",{"path":1768,"title":1769},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fhook-based-plugins-with-pluggy","Hook-Based Plugins for Python CLIs with pluggy",{"path":1771,"title":1772},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis","Plugin Architectures for Extensible CLIs",{"path":1774,"title":1775},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fisolating-plugin-failures","Isolating Plugin Failures in an Extensible Python CLI",{"path":1777,"title":1778},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Ftesting-plugins-against-the-host-cli","Testing Plugins Against the Host CLI",{"path":1780,"title":1781},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fversioning-a-plugin-api","Versioning a Plugin API for a Python CLI",{"path":1783,"title":1784},"\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":1786,"title":1787},"\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":1789,"title":1790},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fdependency-injection-patterns-for-cli-commands","Dependency Injection Patterns for CLI Commands",{"path":1792,"title":1793},"\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":1795,"title":1796},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis","Structuring Multi-Command Python CLIs",{"path":1798,"title":1799},"\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":1801,"title":1802},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fregistering-commands-from-modules-automatically","Registering CLI Commands from Modules Automatically",{"path":1804,"title":1805},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-common-options-across-commands","Sharing Common Options Across Python CLI Commands",{"path":1807,"title":1808},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-state-with-click-context-objects","Sharing State with Click Context Objects",{"path":1810,"title":1811},"\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":1813,"title":1814},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications","Testing Python CLI Applications",{"path":1816,"title":1817},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fmeasuring-cli-test-coverage","Measuring CLI Test Coverage",{"path":1819,"title":1820},"\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":1822,"title":1823},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fproperty-based-testing-cli-arguments-with-hypothesis","Property-Based Testing CLI Arguments with Hypothesis",{"path":1825,"title":1826},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fsnapshot-testing-cli-output","Snapshot Testing CLI Output",{"path":1828,"title":1829},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-click-commands-with-clirunner","Testing Click Commands with CliRunner",{"path":1831,"title":1832},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-commands-that-call-subprocesses","Testing Python CLI Commands That Call Subprocesses",{"path":1834,"title":1835},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-interactive-prompts-and-stdin","Testing Interactive Prompts and stdin",{"path":1837,"title":1838},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftranscript-tests-for-cli-commands","Transcript Tests for Python CLI Commands",{"path":1840,"title":1841},"\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":1843,"title":1844},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fbuilding-dynamic-commands-in-click","Building Dynamic Commands in Click",{"path":1846,"title":1847},"\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":1849,"title":1850},"\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":1852,"title":1853},"\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":1855,"title":1856},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each","Typer vs Click: When to Use Each",{"path":1858,"title":1859},"\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":1861,"title":1862},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Ftyper-callback-functions-explained","Typer callback functions explained",{"path":1864,"title":1865},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fusing-annotated-options-in-typer","Using Annotated Options in Typer",{"path":1867,"title":1868},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fautomating-releases-from-git-tags","Automating Python CLI Releases from Git Tags",{"path":1870,"title":1871},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fcaching-uv-dependencies-in-ci","Caching uv Dependencies in CI for Python CLIs",{"path":1873,"title":1874},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis","CI\u002FCD Pipelines for Python CLIs",{"path":1876,"title":1877},"\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":1879,"title":1880},"\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":1882,"title":1883},"\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":1885,"title":1886},"\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":1888,"title":1889},"\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":1891,"title":1892},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fbuilding-a-cookiecutter-template-for-typer-clis","Building a Cookiecutter Template for Typer CLIs",{"path":1894,"title":1895},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fcopier-vs-cookiecutter-for-cli-templates","Copier vs Cookiecutter for CLI Templates",{"path":1897,"title":1898},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter","CLI Project Scaffolding with Cookiecutter",{"path":1900,"title":1901},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fpost-generation-hooks-in-cli-templates","Post-Generation Hooks in Python CLI Templates",{"path":1903,"title":1904},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftemplate-variables-and-conditional-files","Template Variables and Conditional Files in CLI Templates",{"path":1906,"title":1907},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftesting-a-project-template-with-pytest","Testing a CLI Project Template with pytest",{"path":1909,"title":1910},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fupdating-generated-projects-with-copier-update","Updating Generated CLI Projects with copier update",{"path":1912,"title":1913},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbuilding-cross-platform-release-binaries-in-ci","Building Cross-Platform Release Binaries in CI",{"path":1915,"title":1916},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbundling-a-python-cli-with-pyinstaller","Bundling a Python CLI with PyInstaller",{"path":1918,"title":1919},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fcode-signing-and-notarizing-cli-binaries","Code Signing and Notarizing Python CLI Binaries",{"path":1921,"title":1922},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fhomebrew-and-scoop-packaging-for-python-clis","Homebrew and Scoop Packaging for Python CLIs",{"path":1924,"title":1925},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries","Distributing CLIs as Standalone Binaries",{"path":1927,"title":1928},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fnuitka-vs-pyinstaller-for-python-clis","Nuitka vs PyInstaller for Python CLI Binaries",{"path":1930,"title":1931},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Freducing-pyinstaller-binary-size","Reducing the Size of a PyInstaller CLI Binary",{"path":1933,"title":1934},"\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":1936,"title":1937},"\u002Fproject-setup-dependency-management","Project Setup & Dependency Management",{"path":1939,"title":1940},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fconfiguring-ruff-for-a-cli-project","Configuring Ruff for a Python CLI Project",{"path":1942,"title":1943},"\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":1945,"title":1946},"\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":1948,"title":1949},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code","Linting and Type-Checking Python CLI Code",{"path":1951,"title":1952},"\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":1954,"title":1955},"\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":1957,"title":1958},"\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":1960,"title":1961},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fautomating-changelogs-with-conventional-commits","Automating Changelogs with Conventional Commits",{"path":1963,"title":1964},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fbumping-versions-consistently-across-a-cli-project","Bumping Versions Consistently Across a Python CLI Project",{"path":1966,"title":1967},"\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":1969,"title":1970},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fexposing-version-info-and-build-metadata","Exposing Version Info and Build Metadata",{"path":1972,"title":1973},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs","Managing CLI Versioning & Changelogs",{"path":1975,"title":1976},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fsemantic-versioning-policy-for-cli-tools","A Semantic Versioning Policy for CLI Tools",{"path":1978,"title":1979},"\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":1981,"title":1982},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbuilding-wheels-and-sdists-for-python-clis","Building Wheels and sdists for Python CLIs",{"path":1984,"title":1985},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbundling-data-files-with-importlib-resources","Bundling Data Files with importlib.resources in CLIs",{"path":1987,"title":1988},"\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":1990,"title":1991},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution","Packaging Python CLIs for Distribution",{"path":1993,"title":1994},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Finstalling-and-distributing-clis-with-pipx","Installing and Distributing CLIs with pipx",{"path":1996,"title":1997},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Foptional-dependencies-and-extras-for-clis","Optional Dependencies and Extras for Python CLIs",{"path":1999,"title":2000},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fpublishing-a-python-cli-to-pypi","Publishing a Python CLI to PyPI",{"path":2002,"title":2003},"\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":2005,"title":2006},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fdynamic-versioning-with-poetry-plugins","Dynamic Versioning for a Poetry CLI from Git Tags",{"path":2008,"title":2009},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development","Poetry Workflows for CLI Development",{"path":2011,"title":2012},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fmanaging-poetry-lock-files-for-cli-tools","Managing Poetry Lock Files for CLI Tools",{"path":2014,"title":2015},"\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":2017,"title":2018},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-dependency-groups-for-cli-tooling","Poetry Dependency Groups for CLI Tooling",{"path":2020,"title":2021},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-entry-points-and-scripts-for-clis","Poetry Entry Points and Scripts for CLIs",{"path":2023,"title":2024},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpublishing-a-cli-with-poetry","Building and Publishing a Python CLI with Poetry",{"path":2026,"title":2027},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects","Pre-commit Hooks for CLI Projects",{"path":2029,"title":2030},"\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":2032,"title":2033},"\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":2035,"title":2036},"\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":2038,"title":2039},"\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":2041,"title":2042},"\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":2044,"title":2045},"\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":2047,"title":2048},"\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":2050,"title":2051},"\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":2053,"title":2054},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain","Securing the Supply Chain of a Python CLI",{"path":2056,"title":2057},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpinning-dependencies-with-hashes","Pinning a Python CLI’s Dependencies with Hashes",{"path":2059,"title":2060},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpublishing-attestations-and-verifying-releases","Publishing Attestations and Verifying Python CLI Releases",{"path":2062,"title":2063},"\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":2065,"title":2066},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management","uv for Python CLI Dependency Management",{"path":2068,"title":2069},"\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":2071,"title":2072},"\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":2074,"title":2075},"\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":2077,"title":2078},"\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":2080,"title":1207},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-tool-install-vs-pipx-for-clis",{"path":1251,"title":5},{"path":2083,"title":2084},"\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":2086,"title":2087},"\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":2089,"title":2090},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices","Python CLI Env Isolation Best Practices",{"path":2092,"title":2093},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fisolating-cli-tools-from-project-dependencies","Isolating CLI Tools from Your Project’s Dependencies",{"path":2095,"title":2096},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fmanaging-virtual-environments-for-cross-platform-clis","Managing Python CLI Virtual Environments",{"path":2098,"title":2099},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fpinning-the-python-version-for-a-cli","Pinning the Python Version for a CLI",{"path":2101,"title":2102},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fsupporting-multiple-python-versions-with-nox","Supporting Multiple Python Versions with nox",1790967543095]