[{"data":1,"prerenderedAt":1910},["ShallowReactive",2],{"page-\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Flocking-and-syncing-cli-dependencies-with-uv\u002F":3,"content-directory":1066},{"id":4,"title":5,"body":6,"date":1051,"description":1052,"difficulty":1053,"draft":1054,"extension":1055,"meta":1056,"navigation":464,"path":1057,"seo":1058,"stem":1059,"tags":1060,"updated":1051,"__hash__":1065},"content\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Flocking-and-syncing-cli-dependencies-with-uv\u002Findex.md","Locking and Syncing a Python CLI’s Dependencies with uv",{"type":7,"value":8,"toc":1025},"minimark",[9,40,45,67,71,94,98,116,120,125,205,227,234,263,281,303,306,310,375,396,408,412,418,553,584,588,595,642,658,661,665,668,745,749,752,860,877,881,911,915,922,925,932,949,956,966,974,987,991,1021],[10,11,12,16,17,20,21,25,26,29,30,33,34,39],"p",{},[13,14,15],"code",{},"uv.lock"," is the most important file in a uv-managed CLI project that nobody reads. It records the exact version, source and file hashes of every package your project can install — on every platform and Python version you support — so that a test run on a laptop, a CI job and a release build all see the same dependency set. Two commands work with it: ",[13,18,19],{},"uv lock"," decides ",[22,23,24],"em",{},"what"," the versions are, and ",[13,27,28],{},"uv sync"," makes a virtual environment ",[22,31,32],{},"match"," them. Most of the confusing moments with uv — CI that quietly installs something different, an upgrade that touches forty packages, a merge conflict in a 3,000-line file — come from not knowing which command does what and which flags to use where. This guide sorts that out for a CLI project. It belongs to the ",[35,36,38],"a",{"href":37},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002F","uv topic",".",[41,42,44],"h2",{"id":43},"prerequisites","Prerequisites",[46,47,48,56],"ul",{},[49,50,51,52,55],"li",{},"uv installed (",[13,53,54],{},"curl -LsSf https:\u002F\u002Fastral.sh\u002Fuv\u002Finstall.sh | sh"," or your package manager).",[49,57,58,59,62,63,39],{},"A CLI project with a ",[13,60,61],{},"pyproject.toml",", for example one created as in ",[35,64,66],{"href":65},"\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",[41,68,70],{"id":69},"two-files-two-jobs","Two files, two jobs",[10,72,73,75,76,79,80,83,84,87,88,75,90,93],{},[13,74,61],{}," says what your project ",[22,77,78],{},"accepts",": ranges such as ",[13,81,82],{},"typer>=0.12"," and ",[13,85,86],{},"httpx>=0.27,\u003C1",". Those ranges are what end users get when they install your CLI from PyPI, so they should be permissive enough to receive fixes. ",[13,89,15],{},[22,91,92],{},"uses",": one resolved, hashed version of each package, chosen within those ranges. Committing it means every developer and every CI run starts from the same set.",[95,96],"inline-diagram",{"name":97},"uvlock-two-files",[10,99,100,101,104,105,108,109,111,112,115],{},"The lock file is ",[22,102,103],{},"universal",": uv resolves once for all platforms and Python versions declared by ",[13,106,107],{},"requires-python",", recording platform-specific packages with environment markers. A single ",[13,110,15],{}," therefore serves a Linux CI runner, a macOS laptop and a Windows tester — unlike a ",[13,113,114],{},"requirements.txt"," compiled on one machine.",[41,117,119],{"id":118},"the-recipe","The recipe",[121,122,124],"h3",{"id":123},"day-to-day","Day to day",[126,127,132],"pre",{"className":128,"code":129,"language":130,"meta":131,"style":131},"language-bash shiki shiki-themes github-light github-dark","uv add httpx                 # add to pyproject.toml, re-lock, sync the venv\nuv add --dev pytest respx    # development dependency group\nuv remove rich               # remove, re-lock, sync\nuv run mytool --help         # sync if needed, then run inside the project venv\n","bash","",[13,133,134,154,174,188],{"__ignoreMap":131},[135,136,139,143,147,150],"span",{"class":137,"line":138},"line",1,[135,140,142],{"class":141},"sScJk","uv",[135,144,146],{"class":145},"sZZnC"," add",[135,148,149],{"class":145}," httpx",[135,151,153],{"class":152},"sJ8bj","                 # add to pyproject.toml, re-lock, sync the venv\n",[135,155,157,159,161,165,168,171],{"class":137,"line":156},2,[135,158,142],{"class":141},[135,160,146],{"class":145},[135,162,164],{"class":163},"sj4cs"," --dev",[135,166,167],{"class":145}," pytest",[135,169,170],{"class":145}," respx",[135,172,173],{"class":152},"    # development dependency group\n",[135,175,177,179,182,185],{"class":137,"line":176},3,[135,178,142],{"class":141},[135,180,181],{"class":145}," remove",[135,183,184],{"class":145}," rich",[135,186,187],{"class":152},"               # remove, re-lock, sync\n",[135,189,191,193,196,199,202],{"class":137,"line":190},4,[135,192,142],{"class":141},[135,194,195],{"class":145}," run",[135,197,198],{"class":145}," mytool",[135,200,201],{"class":163}," --help",[135,203,204],{"class":152},"         # sync if needed, then run inside the project venv\n",[10,206,207,210,211,83,214,217,218,220,221,223,224,226],{},[13,208,209],{},"uv add",", ",[13,212,213],{},"uv remove",[13,215,216],{},"uv run"," keep both files and the environment consistent automatically: they update ",[13,219,61],{},", re-lock if the requirements changed, and sync the virtual environment. For most daily work you never call ",[13,222,19],{}," or ",[13,225,28],{}," directly.",[121,228,230,231],{"id":229},"in-ci-locked","In CI: ",[13,232,233],{},"--locked",[126,235,237],{"className":128,"code":236,"language":130,"meta":131,"style":131},"uv sync --locked             # fail if uv.lock does not match pyproject.toml\nuv run --locked pytest\n",[13,238,239,252],{"__ignoreMap":131},[135,240,241,243,246,249],{"class":137,"line":138},[135,242,142],{"class":141},[135,244,245],{"class":145}," sync",[135,247,248],{"class":163}," --locked",[135,250,251],{"class":152},"             # fail if uv.lock does not match pyproject.toml\n",[135,253,254,256,258,260],{"class":137,"line":156},[135,255,142],{"class":141},[135,257,195],{"class":145},[135,259,248],{"class":163},[135,261,262],{"class":145}," pytest\n",[10,264,265,266,268,269,271,272,274,275,277,278,280],{},"Without a flag, ",[13,267,28],{}," re-locks when ",[13,270,61],{}," has changed since the lock was written — convenient locally, dangerous in CI, where it means testing a resolution nobody reviewed. ",[13,273,233],{}," turns that situation into an error: \"The lockfile at ",[13,276,15],{}," needs to be updated\". The contributor then runs ",[13,279,19],{}," and commits the result, and the change shows up in review.",[10,282,283,286,287,289,290,293,294,296,297,299,300,302],{},[13,284,285],{},"--frozen"," is the other strict flag, and the difference matters. ",[13,288,285],{}," uses the lock file ",[22,291,292],{},"as is"," without checking it against ",[13,295,61],{}," at all. Use it where ",[13,298,61],{}," may legitimately differ — in a Docker build stage that copies only the lock file first for layer caching, or when exporting — and use ",[13,301,233],{}," everywhere you want the consistency check.",[95,304],{"name":305},"uvlock-flags",[121,307,309],{"id":308},"upgrading-on-purpose","Upgrading on purpose",[126,311,313],{"className":128,"code":312,"language":130,"meta":131,"style":131},"uv lock --upgrade-package httpx          # move one package (and what it needs)\nuv lock --upgrade-package 'rich\u003C14'      # move it, but not past a bound\nuv lock --upgrade                        # re-resolve everything to the newest allowed\nuv tree --outdated --depth 1             # see what is behind\n",[13,314,315,330,344,356],{"__ignoreMap":131},[135,316,317,319,322,325,327],{"class":137,"line":138},[135,318,142],{"class":141},[135,320,321],{"class":145}," lock",[135,323,324],{"class":163}," --upgrade-package",[135,326,149],{"class":145},[135,328,329],{"class":152},"          # move one package (and what it needs)\n",[135,331,332,334,336,338,341],{"class":137,"line":156},[135,333,142],{"class":141},[135,335,321],{"class":145},[135,337,324],{"class":163},[135,339,340],{"class":145}," 'rich\u003C14'",[135,342,343],{"class":152},"      # move it, but not past a bound\n",[135,345,346,348,350,353],{"class":137,"line":176},[135,347,142],{"class":141},[135,349,321],{"class":145},[135,351,352],{"class":163}," --upgrade",[135,354,355],{"class":152},"                        # re-resolve everything to the newest allowed\n",[135,357,358,360,363,366,369,372],{"class":137,"line":190},[135,359,142],{"class":141},[135,361,362],{"class":145}," tree",[135,364,365],{"class":163}," --outdated",[135,367,368],{"class":163}," --depth",[135,370,371],{"class":163}," 1",[135,373,374],{"class":152},"             # see what is behind\n",[10,376,377,379,380,382,383,386,387,391,392,395],{},[13,378,19],{}," on its own never upgrades anything that still satisfies ",[13,381,61],{},"; it only resolves what is new or no longer valid. That stability is deliberate — upgrades happen when you ask. Targeted upgrades with ",[13,384,385],{},"--upgrade-package"," keep lock diffs small and reviewable, which is also the fastest way to apply a security fix found by ",[35,388,390],{"href":389},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fauditing-dependencies-with-pip-audit\u002F","auditing dependencies with pip-audit",". A full ",[13,393,394],{},"--upgrade"," is best done on a schedule by a bot, as its own pull request, with the test suite as the judge.",[10,397,398,399,402,403,407],{},"To check without writing anything, ",[13,400,401],{},"uv lock --check"," exits non-zero if the lock is out of date — handy in a ",[35,404,406],{"href":405},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects\u002Fsetting-up-pre-commit-for-python-cli-repos\u002F","pre-commit hook"," so the mistake is caught before pushing.",[121,409,411],{"id":410},"dependency-groups-for-a-cli","Dependency groups for a CLI",[10,413,414,415,417],{},"Development tools do not belong in the dependencies users install. uv's dependency groups (PEP 735) keep them separate in ",[13,416,61],{},":",[126,419,423],{"className":420,"code":421,"language":422,"meta":131,"style":131},"language-toml shiki shiki-themes github-light github-dark","[project]\nname = \"mytool\"\ndependencies = [\"typer>=0.12\", \"httpx>=0.27,\u003C1\"]\n\n[project.optional-dependencies]\nyaml = [\"pyyaml>=6\"]                     # an extra users can opt into\n\n[dependency-groups]\ndev = [\"pytest>=8\", \"respx>=0.21\"]\nlint = [\"ruff>=0.6\", \"mypy>=1.11\"]\ndocs = [\"mkdocs-material>=9\"]\n","toml",[13,424,425,437,445,460,466,480,495,500,510,526,542],{"__ignoreMap":131},[135,426,427,431,434],{"class":137,"line":138},[135,428,430],{"class":429},"sVt8B","[",[135,432,433],{"class":141},"project",[135,435,436],{"class":429},"]\n",[135,438,439,442],{"class":137,"line":156},[135,440,441],{"class":429},"name = ",[135,443,444],{"class":145},"\"mytool\"\n",[135,446,447,450,453,455,458],{"class":137,"line":176},[135,448,449],{"class":429},"dependencies = [",[135,451,452],{"class":145},"\"typer>=0.12\"",[135,454,210],{"class":429},[135,456,457],{"class":145},"\"httpx>=0.27,\u003C1\"",[135,459,436],{"class":429},[135,461,462],{"class":137,"line":190},[135,463,465],{"emptyLinePlaceholder":464},true,"\n",[135,467,469,471,473,475,478],{"class":137,"line":468},5,[135,470,430],{"class":429},[135,472,433],{"class":141},[135,474,39],{"class":429},[135,476,477],{"class":141},"optional-dependencies",[135,479,436],{"class":429},[135,481,483,486,489,492],{"class":137,"line":482},6,[135,484,485],{"class":429},"yaml = [",[135,487,488],{"class":145},"\"pyyaml>=6\"",[135,490,491],{"class":429},"]                     ",[135,493,494],{"class":152},"# an extra users can opt into\n",[135,496,498],{"class":137,"line":497},7,[135,499,465],{"emptyLinePlaceholder":464},[135,501,503,505,508],{"class":137,"line":502},8,[135,504,430],{"class":429},[135,506,507],{"class":141},"dependency-groups",[135,509,436],{"class":429},[135,511,513,516,519,521,524],{"class":137,"line":512},9,[135,514,515],{"class":429},"dev = [",[135,517,518],{"class":145},"\"pytest>=8\"",[135,520,210],{"class":429},[135,522,523],{"class":145},"\"respx>=0.21\"",[135,525,436],{"class":429},[135,527,529,532,535,537,540],{"class":137,"line":528},10,[135,530,531],{"class":429},"lint = [",[135,533,534],{"class":145},"\"ruff>=0.6\"",[135,536,210],{"class":429},[135,538,539],{"class":145},"\"mypy>=1.11\"",[135,541,436],{"class":429},[135,543,545,548,551],{"class":137,"line":544},11,[135,546,547],{"class":429},"docs = [",[135,549,550],{"class":145},"\"mkdocs-material>=9\"",[135,552,436],{"class":429},[10,554,555,556,558,559,562,563,566,567,570,571,575,576,579,580,39],{},"All groups are locked together, so the lock covers everything, and syncs choose what to install: ",[13,557,28],{}," installs the project plus the ",[13,560,561],{},"dev"," group by default; ",[13,564,565],{},"uv sync --group lint"," adds linters; ",[13,568,569],{},"uv sync --no-dev"," gives exactly what users get, which is what a release build or a ",[35,572,574],{"href":573},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fsmoke-testing-the-built-wheel-in-ci\u002F","smoke test of the built wheel"," should use. Extras are different: they are published with your package and users install them with ",[13,577,578],{},"mytool[yaml]"," — see ",[35,581,583],{"href":582},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Foptional-dependencies-and-extras-for-clis\u002F","optional dependencies and extras for CLIs",[41,585,587],{"id":586},"reading-a-lock-diff","Reading a lock diff",[10,589,590,591,594],{},"A lock change in a pull request is worth thirty seconds of attention. Each package appears as a ",[13,592,593],{},"[[package]]"," table with its name, version, source and hashes; a diff of a targeted upgrade looks like this:",[126,596,600],{"className":597,"code":598,"language":599,"meta":131,"style":131},"language-diff shiki shiki-themes github-light github-dark"," [[package]]\n name = \"httpx\"\n-version = \"0.27.2\"\n-source = { registry = \"https:\u002F\u002Fpypi.org\u002Fsimple\" }\n-sdist = { url = \"…\u002Fhttpx-0.27.2.tar.gz\", hash = \"sha256:f7c2…\" }\n+version = \"0.28.1\"\n+source = { registry = \"https:\u002F\u002Fpypi.org\u002Fsimple\" }\n+sdist = { url = \"…\u002Fhttpx-0.28.1.tar.gz\", hash = \"sha256:75e9…\" }\n","diff",[13,601,602,607,612,617,622,627,632,637],{"__ignoreMap":131},[135,603,604],{"class":137,"line":138},[135,605,606],{}," [[package]]\n",[135,608,609],{"class":137,"line":156},[135,610,611],{}," name = \"httpx\"\n",[135,613,614],{"class":137,"line":176},[135,615,616],{},"-version = \"0.27.2\"\n",[135,618,619],{"class":137,"line":190},[135,620,621],{},"-source = { registry = \"https:\u002F\u002Fpypi.org\u002Fsimple\" }\n",[135,623,624],{"class":137,"line":468},[135,625,626],{},"-sdist = { url = \"…\u002Fhttpx-0.27.2.tar.gz\", hash = \"sha256:f7c2…\" }\n",[135,628,629],{"class":137,"line":482},[135,630,631],{},"+version = \"0.28.1\"\n",[135,633,634],{"class":137,"line":497},[135,635,636],{},"+source = { registry = \"https:\u002F\u002Fpypi.org\u002Fsimple\" }\n",[135,638,639],{"class":137,"line":502},[135,640,641],{},"+sdist = { url = \"…\u002Fhttpx-0.28.1.tar.gz\", hash = \"sha256:75e9…\" }\n",[10,643,644,645,649,650,653,654,657],{},"Three things are worth checking. ",[646,647,648],"strong",{},"Unexpected packages"," — a new name you did not add means a dependency gained a dependency; make sure it is the package you think it is. ",[646,651,652],{},"Changed sources"," — a package moving from PyPI to another index or a git URL deserves a question. ",[646,655,656],{},"Size of the change"," — a \"small\" upgrade that touches dozens of packages usually means a range was too loose or the wrong command was used.",[95,659],{"name":660},"uvlock-terminal",[41,662,664],{"id":663},"ux-considerations","UX considerations",[10,666,667],{},"The \"users\" here are your contributors, and a few conventions make the lock painless for them:",[46,669,670,683,697,714,727],{},[49,671,672,677,678,680,681,39],{},[646,673,674,675,39],{},"Never hand-edit ",[13,676,15],{}," Resolve merge conflicts by taking either side and running ",[13,679,19],{}," again; uv rebuilds a consistent file from ",[13,682,61],{},[49,684,685,688,689,692,693,696],{},[646,686,687],{},"Mark it generated"," in ",[13,690,691],{},".gitattributes"," (",[13,694,695],{},"uv.lock linguist-generated=true",") so code review tools collapse it by default, while still showing it on demand.",[49,698,699,702,703,705,706,709,710,713],{},[646,700,701],{},"Write the commands in CONTRIBUTING.md."," \"Use ",[13,704,209],{},", never ",[13,707,708],{},"pip install","; CI runs ",[13,711,712],{},"uv sync --locked",".\" One paragraph prevents most lock-related CI failures.",[49,715,716,692,719,722,723,726],{},[646,717,718],{},"Pin uv itself in CI",[13,720,721],{},"astral-sh\u002Fsetup-uv"," with a ",[13,724,725],{},"version:",") so a new uv release cannot change resolution behaviour mid-sprint; upgrade it deliberately like any other tool.",[49,728,729,735,736,739,740,744],{},[646,730,731,732,734],{},"Keep ",[13,733,107],{}," honest."," The lock is resolved for every Python version it allows; claiming ",[13,737,738],{},">=3.8"," when you only test 3.11+ makes resolution harder and the lock larger. ",[35,741,743],{"href":742},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fpinning-the-python-version-for-a-cli\u002F","Pinning the Python version for a CLI"," covers the trade-off.",[41,746,748],{"id":747},"testing-the-behaviour","Testing the behaviour",[10,750,751],{},"The behaviour to guarantee is that CI fails when the lock is stale. Add a job step and, once, prove it works:",[126,753,757],{"className":754,"code":755,"language":756,"meta":131,"style":131},"language-yaml shiki shiki-themes github-light github-dark","# .github\u002Fworkflows\u002Ftest.yml (excerpt)\n      - uses: astral-sh\u002Fsetup-uv@v6\n        with:\n          version: \"0.8.x\"\n          enable-cache: true\n      - name: Check the lock file is current\n        run: uv lock --check\n      - name: Install exactly the locked set\n        run: uv sync --locked --all-groups\n      - run: uv run --locked pytest\n","yaml",[13,758,759,764,778,786,796,806,818,828,839,848],{"__ignoreMap":131},[135,760,761],{"class":137,"line":138},[135,762,763],{"class":152},"# .github\u002Fworkflows\u002Ftest.yml (excerpt)\n",[135,765,766,769,772,775],{"class":137,"line":156},[135,767,768],{"class":429},"      - ",[135,770,92],{"class":771},"s9eBZ",[135,773,774],{"class":429},": ",[135,776,777],{"class":145},"astral-sh\u002Fsetup-uv@v6\n",[135,779,780,783],{"class":137,"line":176},[135,781,782],{"class":771},"        with",[135,784,785],{"class":429},":\n",[135,787,788,791,793],{"class":137,"line":190},[135,789,790],{"class":771},"          version",[135,792,774],{"class":429},[135,794,795],{"class":145},"\"0.8.x\"\n",[135,797,798,801,803],{"class":137,"line":468},[135,799,800],{"class":771},"          enable-cache",[135,802,774],{"class":429},[135,804,805],{"class":163},"true\n",[135,807,808,810,813,815],{"class":137,"line":482},[135,809,768],{"class":429},[135,811,812],{"class":771},"name",[135,814,774],{"class":429},[135,816,817],{"class":145},"Check the lock file is current\n",[135,819,820,823,825],{"class":137,"line":497},[135,821,822],{"class":771},"        run",[135,824,774],{"class":429},[135,826,827],{"class":145},"uv lock --check\n",[135,829,830,832,834,836],{"class":137,"line":502},[135,831,768],{"class":429},[135,833,812],{"class":771},[135,835,774],{"class":429},[135,837,838],{"class":145},"Install exactly the locked set\n",[135,840,841,843,845],{"class":137,"line":512},[135,842,822],{"class":771},[135,844,774],{"class":429},[135,846,847],{"class":145},"uv sync --locked --all-groups\n",[135,849,850,852,855,857],{"class":137,"line":528},[135,851,768],{"class":429},[135,853,854],{"class":771},"run",[135,856,774],{"class":429},[135,858,859],{"class":145},"uv run --locked pytest\n",[10,861,862,863,865,866,868,869,871,872,876],{},"To see the failure, change a version bound in ",[13,864,61],{}," on a branch without running ",[13,867,19],{},", push, and confirm the \"Check the lock file\" step fails with a message naming ",[13,870,15],{},". Combined with ",[35,873,875],{"href":874},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fcaching-uv-dependencies-in-ci\u002F","caching uv dependencies in CI",", the strict install adds almost no time to the job.",[41,878,880],{"id":879},"conclusion","Conclusion",[10,882,883,885,886,888,889,210,891,83,893,895,896,898,899,901,902,904,905,907,908,910],{},[13,884,19],{}," decides versions; ",[13,887,28],{}," applies them. Let ",[13,890,209],{},[13,892,213],{},[13,894,216],{}," keep everything consistent while you work; use ",[13,897,233],{}," in CI so stale locks fail loudly; reserve ",[13,900,285],{}," for the few places that must ignore ",[13,903,61],{},"; upgrade deliberately with ",[13,906,385],{},"; and keep development tools in dependency groups so ",[13,909,569],{}," reproduces exactly what users get. The lock file then does its job quietly: everyone, everywhere, tests the same thing.",[41,912,914],{"id":913},"frequently-asked-questions","Frequently asked questions",[121,916,918,919,921],{"id":917},"should-a-cli-commit-uvlock","Should a CLI commit ",[13,920,15],{},"?",[10,923,924],{},"Yes. Even though users installing from PyPI resolve from your ranges instead, the lock makes development, CI and release builds reproducible, and it is the source for SBOMs, audits and hashed exports. Libraries debate this; applications and CLIs should commit it.",[121,926,928,929,931],{"id":927},"why-did-uv-run-change-my-lock-file","Why did ",[13,930,216],{}," change my lock file?",[10,933,934,935,937,938,940,941,944,945,948],{},"Because ",[13,936,61],{}," changed — someone edited a bound by hand, or a merge brought in a new dependency — and ",[13,939,216],{}," re-locks to keep things consistent. Use ",[13,942,943],{},"uv run --locked"," (or set ",[13,946,947],{},"UV_LOCKED=1",") where that should be an error instead.",[121,950,952,953,955],{"id":951},"how-do-i-get-a-requirementstxt-for-tools-that-need-one","How do I get a ",[13,954,114],{}," for tools that need one?",[10,957,958,961,962,39],{},[13,959,960],{},"uv export --format requirements.txt --no-dev -o requirements.txt"," writes a fully pinned, hashed file from the lock. Regenerate it rather than editing it, as described in ",[35,963,965],{"href":964},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpinning-dependencies-with-hashes\u002F","pinning dependencies with hashes",[121,967,969,970,973],{"id":968},"what-does-inexact-do","What does ",[13,971,972],{},"--inexact"," do?",[10,975,976,977,979,980,983,984,986],{},"By default ",[13,978,28],{}," makes the environment ",[22,981,982],{},"exactly"," match the lock, removing packages that are not in it. ",[13,985,972],{}," leaves extra packages alone — occasionally useful when you installed a debugging tool by hand, but CI should always use the default exact sync.",[41,988,990],{"id":989},"related","Related",[46,992,993,999,1005,1011,1016],{},[49,994,995,996],{},"Up: ",[35,997,998],{"href":37},"uv for Python CLI dependency management",[49,1000,1001],{},[35,1002,1004],{"href":1003},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis\u002F","uv workspaces for multi-package CLIs",[49,1006,1007],{},[35,1008,1010],{"href":1009},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fmigrating-a-cli-from-poetry-to-uv\u002F","Migrating a CLI from Poetry to uv",[49,1012,1013],{},[35,1014,1015],{"href":874},"Caching uv dependencies in CI",[49,1017,1018],{},[35,1019,1020],{"href":964},"Pinning dependencies with hashes",[1022,1023,1024],"style",{},"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 .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}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 .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}",{"title":131,"searchDepth":156,"depth":156,"links":1026},[1027,1028,1029,1036,1037,1038,1039,1040,1050],{"id":43,"depth":156,"text":44},{"id":69,"depth":156,"text":70},{"id":118,"depth":156,"text":119,"children":1030},[1031,1032,1034,1035],{"id":123,"depth":176,"text":124},{"id":229,"depth":176,"text":1033},"In CI: --locked",{"id":308,"depth":176,"text":309},{"id":410,"depth":176,"text":411},{"id":586,"depth":156,"text":587},{"id":663,"depth":156,"text":664},{"id":747,"depth":156,"text":748},{"id":879,"depth":156,"text":880},{"id":913,"depth":156,"text":914,"children":1041},[1042,1044,1046,1048],{"id":917,"depth":176,"text":1043},"Should a CLI commit uv.lock?",{"id":927,"depth":176,"text":1045},"Why did uv run change my lock file?",{"id":951,"depth":176,"text":1047},"How do I get a requirements.txt for tools that need one?",{"id":968,"depth":176,"text":1049},"What does --inexact do?",{"id":989,"depth":156,"text":990},"2026-10-02","Understand uv.lock in a CLI project: lock vs sync, --locked and --frozen in CI, targeted upgrades, reading lock diffs and dependency groups.","beginner",false,"md",{},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Flocking-and-syncing-cli-dependencies-with-uv",{"title":5,"description":1052},"project-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Flocking-and-syncing-cli-dependencies-with-uv\u002Findex",[142,1061,1062,1063,1064],"lockfile","dependencies","ci","reproducibility","_N1PCrb4YaJ7Evun5F6fAxKBn93WW9vc-STsnupl1jA",[1067,1070,1073,1076,1079,1082,1085,1088,1091,1094,1097,1100,1103,1106,1109,1112,1115,1118,1121,1124,1127,1130,1133,1136,1139,1142,1145,1148,1151,1154,1157,1160,1163,1166,1169,1172,1175,1178,1181,1184,1187,1190,1193,1196,1199,1202,1205,1208,1211,1214,1217,1220,1223,1226,1229,1232,1235,1238,1241,1244,1247,1250,1253,1256,1259,1262,1265,1268,1271,1274,1277,1280,1283,1286,1289,1292,1295,1298,1301,1304,1307,1310,1313,1316,1319,1322,1325,1328,1331,1334,1337,1340,1343,1346,1349,1352,1355,1358,1361,1364,1367,1370,1373,1376,1379,1382,1385,1388,1391,1394,1397,1400,1403,1406,1409,1412,1415,1418,1421,1424,1427,1430,1433,1436,1439,1442,1445,1448,1451,1454,1457,1460,1463,1466,1469,1472,1475,1478,1481,1484,1487,1490,1493,1496,1499,1502,1505,1508,1511,1514,1517,1520,1523,1526,1529,1532,1535,1538,1541,1544,1547,1550,1553,1556,1559,1562,1565,1568,1571,1574,1577,1580,1583,1586,1589,1592,1595,1598,1601,1604,1607,1610,1613,1616,1619,1622,1625,1628,1631,1634,1637,1640,1643,1646,1649,1652,1655,1658,1661,1664,1667,1670,1673,1676,1679,1682,1685,1688,1691,1694,1697,1700,1703,1706,1709,1712,1715,1718,1721,1724,1727,1730,1733,1736,1739,1742,1745,1748,1751,1754,1757,1760,1763,1766,1769,1772,1775,1778,1781,1784,1787,1790,1793,1796,1799,1802,1805,1808,1811,1814,1817,1820,1823,1826,1829,1832,1835,1838,1841,1844,1847,1850,1853,1856,1859,1862,1865,1868,1871,1874,1875,1878,1881,1883,1886,1889,1892,1895,1898,1901,1904,1907],{"path":1068,"title":1069},"\u002Fabout","About Python CLI Toolcraft",{"path":1071,"title":1072},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies","Advanced Argument Validation Strategies",{"path":1074,"title":1075},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fparsing-nested-json-arguments-in-python-clis","Parsing Nested JSON Args in Python CLIs",{"path":1077,"title":1078},"\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":1080,"title":1081},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-dependent-and-conflicting-options","Validating Dependent and Conflicting CLI Options",{"path":1083,"title":1084},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-file-and-directory-paths-in-clis","Validating File and Directory Paths in CLIs",{"path":1086,"title":1087},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-urls-hosts-and-ports","Validating URLs, Hosts and Ports in Python CLI Arguments",{"path":1089,"title":1090},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fwriting-custom-click-parameter-types","Writing Custom Click Parameter Types",{"path":1092,"title":1093},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fbrowsing-records-with-a-textual-datatable","Browsing Records with a Textual DataTable Picker",{"path":1095,"title":1096},"\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":1098,"title":1099},"\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":1101,"title":1102},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual","Building Terminal UIs with Textual for Python CLIs",{"path":1104,"title":1105},"\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":1107,"title":1108},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fstyling-textual-apps-with-tcss","Styling Textual Apps with TCSS",{"path":1110,"title":1111},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Ftesting-textual-apps-with-pilot","Testing Textual Apps with Pilot",{"path":1113,"title":1114},"\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":1116,"title":1117},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fdocumenting-environment-variables-in-help","Documenting Environment Variables in CLI Help",{"path":1119,"title":1120},"\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":1122,"title":1123},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation","CLI Help Output and Documentation",{"path":1125,"title":1126},"\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":1128,"title":1129},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fversioning-and-deprecating-cli-flags","Versioning and Deprecating CLI Flags",{"path":1131,"title":1132},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fwriting-help-text-users-actually-read","Writing Help Text Users Actually Read",{"path":1134,"title":1135},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fadapting-output-to-terminal-width","Adapting Python CLI Output to Terminal Width",{"path":1137,"title":1138},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fdetecting-ci-environments-and-non-interactive-shells","Detecting CI Environments and Non-Interactive Shells",{"path":1140,"title":1141},"\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":1143,"title":1144},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fhandling-ansi-escape-codes-on-windows-consoles","Handling ANSI Escape Codes on Windows Consoles",{"path":1146,"title":1147},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility","Cross-Platform Terminal Compatibility for Python CLIs",{"path":1149,"title":1150},"\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":1152,"title":1153},"\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":1155,"title":1156},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fchoosing-exit-codes-for-cli-tools","Choosing Exit Codes for CLI Tools",{"path":1158,"title":1159},"\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":1161,"title":1162},"\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":1164,"title":1165},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Ffriendly-error-messages-and-tracebacks","Friendly Error Messages and Tracebacks",{"path":1167,"title":1168},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fhandling-keyboard-interrupt-cleanly","Handling Keyboard Interrupt Cleanly",{"path":1170,"title":1171},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes","Error Handling and Exit Codes for CLIs",{"path":1173,"title":1174},"\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":1176,"title":1177},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fwriting-crash-reports-users-can-send","Writing Crash Reports Users Can Send",{"path":1179,"title":1180},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Fconfig-precedence-flags-env-files-defaults","Config Precedence: Flags, Env, Files, Defaults",{"path":1182,"title":1183},"\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":1185,"title":1186},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars","Handling Config Files and Env Vars in CLIs",{"path":1188,"title":1189},"\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":1191,"title":1192},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Freading-toml-config-with-tomllib","Reading TOML Config with tomllib in Python CLIs",{"path":1194,"title":1195},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Ftyped-settings-with-pydantic-settings","Typed Settings with pydantic-settings in Python CLIs",{"path":1197,"title":1198},"\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":1200,"title":1201},"\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":1203,"title":1204},"\u002Fadvanced-input-parsing-user-experience","Advanced Input Parsing for Python CLIs",{"path":1206,"title":1207},"\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":1209,"title":1210},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Fbuilding-interactive-prompts-and-menus","Building Interactive Prompts and Menus in Python CLIs",{"path":1212,"title":1213},"\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":1215,"title":1216},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich","Interactive Terminal UI with Rich",{"path":1218,"title":1219},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Flive-dashboards-with-rich-live","Live Dashboards with Rich Live in Python CLIs",{"path":1221,"title":1222},"\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":1224,"title":1225},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Frendering-tables-and-json-with-rich","Rendering Tables and JSON with Rich",{"path":1227,"title":1228},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Ftheming-rich-output-consistently","Theming Rich Output Consistently in Python CLIs",{"path":1230,"title":1231},"\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":1233,"title":1234},"\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":1236,"title":1237},"\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":1239,"title":1240},"\u002Fadvanced-input-parsing-user-experience\u002Foutput-formats-for-data-clis","Output Formats for Data-Heavy Python CLIs",{"path":1242,"title":1243},"\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":1245,"title":1246},"\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":1248,"title":1249},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fargcomplete-for-argparse-clis","Tab Completion for argparse CLIs with argcomplete",{"path":1251,"title":1252},"\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":1254,"title":1255},"\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":1257,"title":1258},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis","Shell Completion for Python CLIs",{"path":1260,"title":1261},"\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":1263,"title":1264},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fshipping-completion-scripts-with-packages","Shipping Shell Completion Scripts with a Python CLI",{"path":1266,"title":1267},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Ftesting-shell-completion-in-python-clis","Testing Shell Completion in Python CLIs",{"path":1269,"title":1270},"\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":1272,"title":1273},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fadding-verbose-and-quiet-logging-flags","Adding Verbose and Quiet Logging Flags",{"path":1275,"title":1276},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps","Structured Logging for CLI Apps",{"path":1278,"title":1279},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Flogging-with-structlog-in-a-cli","Logging with structlog in a Python CLI",{"path":1281,"title":1282},"\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":1284,"title":1285},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fstructured-json-logging-in-python-clis","Structured JSON Logging in Python CLIs",{"path":1287,"title":1288},"\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":1290,"title":1291},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fdetecting-tty-and-adapting-output","Detecting a TTY and Adapting Output",{"path":1293,"title":1294},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Femitting-json-output-for-scripting","Emitting JSON Output for Scripting",{"path":1296,"title":1297},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fhandling-broken-pipe-and-sigpipe","Handling Broken Pipe and SIGPIPE",{"path":1299,"title":1300},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes","Working with stdin, stdout and Pipes",{"path":1302,"title":1303},"\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":1305,"title":1306},"\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":1308,"title":1309},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Freading-piped-input-in-python-clis","Reading Piped Input in Python CLIs",{"path":1311,"title":1312},"\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":1314,"title":1315},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fdownloading-files-with-progress-in-python","Downloading Files with Progress in Python CLIs",{"path":1317,"title":1318},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis","Calling HTTP APIs from Python CLIs",{"path":1320,"title":1321},"\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":1323,"title":1324},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Foauth-device-flow-login-for-clis","OAuth Device Flow Login for Python CLIs",{"path":1326,"title":1327},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fpaginating-api-results-in-a-cli","Paginating API Results in a Python CLI",{"path":1329,"title":1330},"\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":1332,"title":1333},"\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":1335,"title":1336},"\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":1338,"title":1339},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis","Concurrency and Async in Python CLIs",{"path":1341,"title":1342},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fmultiprocessing-for-cpu-bound-cli-tasks","Multiprocessing for CPU-Bound CLI Tasks",{"path":1344,"title":1345},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fparallelising-cli-work-with-thread-pools","Parallelising CLI Work with Thread Pools",{"path":1347,"title":1348},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Frate-limiting-concurrent-requests-in-clis","Rate-Limiting Concurrent Requests in Python CLIs",{"path":1350,"title":1351},"\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":1353,"title":1354},"\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":1356,"title":1357},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fstructured-concurrency-with-taskgroups-in-clis","Structured Concurrency with TaskGroups in Python CLIs",{"path":1359,"title":1360},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fcross-platform-paths-with-pathlib","Cross-Platform Paths with pathlib in CLIs",{"path":1362,"title":1363},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Ffile-locking-for-concurrent-cli-runs","File Locking for Concurrent CLI Runs in Python",{"path":1365,"title":1366},"\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":1368,"title":1369},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes","Filesystem Paths and Atomic Writes for CLIs",{"path":1371,"title":1372},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fsafe-temporary-files-and-directories","Safe Temporary Files and Directories in CLIs",{"path":1374,"title":1375},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fstoring-app-data-with-platformdirs","Storing CLI App Data with platformdirs",{"path":1377,"title":1378},"\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":1380,"title":1381},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fwriting-files-atomically-in-python-clis","Writing Files Atomically in Python CLIs",{"path":1383,"title":1384},"\u002Fcli-runtime-systems-integration","CLI Runtime & Systems Integration for Python",{"path":1386,"title":1387},"\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":1389,"title":1390},"\u002Fcli-runtime-systems-integration\u002Flocal-state-and-sqlite-in-python-clis","Local State and SQLite in Python CLIs",{"path":1392,"title":1393},"\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":1395,"title":1396},"\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":1398,"title":1399},"\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":1401,"title":1402},"\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":1404,"title":1405},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fhandling-sigterm-and-graceful-shutdown","Handling SIGTERM and Graceful Shutdown in CLIs",{"path":1407,"title":1408},"\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":1410,"title":1411},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis","Long-Running and Watch-Mode Python CLIs",{"path":1413,"title":1414},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Freloading-config-on-sighup","Reloading Configuration on SIGHUP in a Python CLI",{"path":1416,"title":1417},"\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":1419,"title":1420},"\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":1422,"title":1423},"\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":1425,"title":1426},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Favoiding-shell-injection-in-python-clis","Avoiding Shell Injection in Python CLIs",{"path":1428,"title":1429},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fcalling-external-commands-safely-with-subprocess","Calling External Commands Safely with subprocess",{"path":1431,"title":1432},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fhandling-subprocess-timeouts-and-exit-codes","Handling Subprocess Timeouts and Exit Codes",{"path":1434,"title":1435},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis","Running Subprocesses from Python CLIs",{"path":1437,"title":1438},"\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":1440,"title":1441},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fpiping-between-subprocesses-in-python","Piping Between Subprocesses in Python Without a Shell",{"path":1443,"title":1444},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fstreaming-subprocess-output-in-real-time","Streaming Subprocess Output in Real Time",{"path":1446,"title":1447},"\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":1449,"title":1450},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis","Secrets and Credentials in Python CLIs",{"path":1452,"title":1453},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fprompting-for-passwords-securely","Prompting for Passwords Securely in Python CLIs",{"path":1455,"title":1456},"\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":1458,"title":1459},"\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":1461,"title":1462},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Frefreshing-expired-tokens-automatically","Refreshing Expired Tokens Automatically in a Python CLI",{"path":1464,"title":1465},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fstoring-tokens-with-keyring","Storing CLI Tokens Securely with keyring",{"path":1467,"title":1468},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fsupporting-multiple-profiles-and-accounts","Supporting Multiple Profiles and Accounts in CLIs",{"path":1470,"title":1471},"\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":1473,"title":1474},"\u002Fcli-runtime-systems-integration\u002Fupdate-checks-and-self-updating-clis","Update Checks, Upgrade Commands and Telemetry for Python CLIs",{"path":1476,"title":1477},"\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":1479,"title":1480},"\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":1482,"title":1483},"\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":1485,"title":1486},"\u002F","Python CLI Toolcraft",{"path":1488,"title":1489},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cleo","Building a Python CLI with Cleo Command Classes",{"path":1491,"title":1492},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cyclopts","Building a Type-Hinted Python CLI with Cyclopts",{"path":1494,"title":1495},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks","Beyond Click and Typer: Alternative Python CLI Frameworks",{"path":1497,"title":1498},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fquick-clis-from-functions-with-python-fire","Quick CLIs from Functions with Python Fire",{"path":1500,"title":1501},"\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":1503,"title":1504},"\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":1506,"title":1507},"\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":1509,"title":1510},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fguarding-startup-with-import-tests","Guarding CLI Startup with Import Tests",{"path":1512,"title":1513},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading","CLI Startup Performance and Lazy Loading",{"path":1515,"title":1516},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Flazy-loading-subcommands-for-faster-startup","Lazy Loading Subcommands for Faster Startup",{"path":1518,"title":1519},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fprofiling-python-cli-startup-time","Profiling Python CLI Startup Time",{"path":1521,"title":1522},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Freducing-cli-dependency-weight","Reducing CLI Dependency Weight",{"path":1524,"title":1525},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-subparsers-for-subcommands","argparse Subparsers for Subcommands",{"path":1527,"title":1528},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-vs-click-vs-typer-comparison","argparse vs Click vs Typer Compared",{"path":1530,"title":1531},"\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":1533,"title":1534},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse","Command-Line Parsing with argparse",{"path":1536,"title":1537},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmigrating-from-argparse-to-typer","Migrating from argparse to Typer",{"path":1539,"title":1540},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmutually-exclusive-options-in-argparse","Mutually Exclusive Options in argparse",{"path":1542,"title":1543},"\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":1545,"title":1546},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fwriting-custom-argparse-actions","Writing Custom argparse Actions in Python",{"path":1548,"title":1549},"\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":1551,"title":1552},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fdesigning-idempotent-commands","Designing Idempotent Commands in a Python CLI",{"path":1554,"title":1555},"\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":1557,"title":1558},"\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":1560,"title":1561},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions","Designing CLI Interfaces and Conventions in Python",{"path":1563,"title":1564},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fnaming-commands-and-flags-consistently","Naming Commands and Flags Consistently in Python CLIs",{"path":1566,"title":1567},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fpositional-arguments-vs-options","Positional Arguments vs Options: Designing a CLI Signature",{"path":1569,"title":1570},"\u002Fmodern-python-cli-frameworks-architecture","Python CLI Frameworks and Architecture",{"path":1572,"title":1573},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fdiscovering-plugins-with-entry-points","Discovering Plugins with Entry Points in Python CLIs",{"path":1575,"title":1576},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fhook-based-plugins-with-pluggy","Hook-Based Plugins for Python CLIs with pluggy",{"path":1578,"title":1579},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis","Plugin Architectures for Extensible CLIs",{"path":1581,"title":1582},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fisolating-plugin-failures","Isolating Plugin Failures in an Extensible Python CLI",{"path":1584,"title":1585},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Ftesting-plugins-against-the-host-cli","Testing Plugins Against the Host CLI",{"path":1587,"title":1588},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fversioning-a-plugin-api","Versioning a Plugin API for a Python CLI",{"path":1590,"title":1591},"\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":1593,"title":1594},"\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":1596,"title":1597},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fdependency-injection-patterns-for-cli-commands","Dependency Injection Patterns for CLI Commands",{"path":1599,"title":1600},"\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":1602,"title":1603},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis","Structuring Multi-Command Python CLIs",{"path":1605,"title":1606},"\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":1608,"title":1609},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fregistering-commands-from-modules-automatically","Registering CLI Commands from Modules Automatically",{"path":1611,"title":1612},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-common-options-across-commands","Sharing Common Options Across Python CLI Commands",{"path":1614,"title":1615},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-state-with-click-context-objects","Sharing State with Click Context Objects",{"path":1617,"title":1618},"\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":1620,"title":1621},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications","Testing Python CLI Applications",{"path":1623,"title":1624},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fmeasuring-cli-test-coverage","Measuring CLI Test Coverage",{"path":1626,"title":1627},"\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":1629,"title":1630},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fproperty-based-testing-cli-arguments-with-hypothesis","Property-Based Testing CLI Arguments with Hypothesis",{"path":1632,"title":1633},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fsnapshot-testing-cli-output","Snapshot Testing CLI Output",{"path":1635,"title":1636},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-click-commands-with-clirunner","Testing Click Commands with CliRunner",{"path":1638,"title":1639},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-commands-that-call-subprocesses","Testing Python CLI Commands That Call Subprocesses",{"path":1641,"title":1642},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-interactive-prompts-and-stdin","Testing Interactive Prompts and stdin",{"path":1644,"title":1645},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftranscript-tests-for-cli-commands","Transcript Tests for Python CLI Commands",{"path":1647,"title":1648},"\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":1650,"title":1651},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fbuilding-dynamic-commands-in-click","Building Dynamic Commands in Click",{"path":1653,"title":1654},"\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":1656,"title":1657},"\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":1659,"title":1660},"\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":1662,"title":1663},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each","Typer vs Click: When to Use Each",{"path":1665,"title":1666},"\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":1668,"title":1669},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Ftyper-callback-functions-explained","Typer callback functions explained",{"path":1671,"title":1672},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fusing-annotated-options-in-typer","Using Annotated Options in Typer",{"path":1674,"title":1675},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fautomating-releases-from-git-tags","Automating Python CLI Releases from Git Tags",{"path":1677,"title":1678},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fcaching-uv-dependencies-in-ci","Caching uv Dependencies in CI for Python CLIs",{"path":1680,"title":1681},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis","CI\u002FCD Pipelines for Python CLIs",{"path":1683,"title":1684},"\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":1686,"title":1687},"\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":1689,"title":1690},"\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":1692,"title":1693},"\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":1695,"title":1696},"\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":1698,"title":1699},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fbuilding-a-cookiecutter-template-for-typer-clis","Building a Cookiecutter Template for Typer CLIs",{"path":1701,"title":1702},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fcopier-vs-cookiecutter-for-cli-templates","Copier vs Cookiecutter for CLI Templates",{"path":1704,"title":1705},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter","CLI Project Scaffolding with Cookiecutter",{"path":1707,"title":1708},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fpost-generation-hooks-in-cli-templates","Post-Generation Hooks in Python CLI Templates",{"path":1710,"title":1711},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftemplate-variables-and-conditional-files","Template Variables and Conditional Files in CLI Templates",{"path":1713,"title":1714},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftesting-a-project-template-with-pytest","Testing a CLI Project Template with pytest",{"path":1716,"title":1717},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fupdating-generated-projects-with-copier-update","Updating Generated CLI Projects with copier update",{"path":1719,"title":1720},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbuilding-cross-platform-release-binaries-in-ci","Building Cross-Platform Release Binaries in CI",{"path":1722,"title":1723},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbundling-a-python-cli-with-pyinstaller","Bundling a Python CLI with PyInstaller",{"path":1725,"title":1726},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fcode-signing-and-notarizing-cli-binaries","Code Signing and Notarizing Python CLI Binaries",{"path":1728,"title":1729},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fhomebrew-and-scoop-packaging-for-python-clis","Homebrew and Scoop Packaging for Python CLIs",{"path":1731,"title":1732},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries","Distributing CLIs as Standalone Binaries",{"path":1734,"title":1735},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fnuitka-vs-pyinstaller-for-python-clis","Nuitka vs PyInstaller for Python CLI Binaries",{"path":1737,"title":1738},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Freducing-pyinstaller-binary-size","Reducing the Size of a PyInstaller CLI Binary",{"path":1740,"title":1741},"\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":1743,"title":1744},"\u002Fproject-setup-dependency-management","Project Setup & Dependency Management",{"path":1746,"title":1747},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fconfiguring-ruff-for-a-cli-project","Configuring Ruff for a Python CLI Project",{"path":1749,"title":1750},"\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":1752,"title":1753},"\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":1755,"title":1756},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code","Linting and Type-Checking Python CLI Code",{"path":1758,"title":1759},"\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":1761,"title":1762},"\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":1764,"title":1765},"\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":1767,"title":1768},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fautomating-changelogs-with-conventional-commits","Automating Changelogs with Conventional Commits",{"path":1770,"title":1771},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fbumping-versions-consistently-across-a-cli-project","Bumping Versions Consistently Across a Python CLI Project",{"path":1773,"title":1774},"\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":1776,"title":1777},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fexposing-version-info-and-build-metadata","Exposing Version Info and Build Metadata",{"path":1779,"title":1780},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs","Managing CLI Versioning & Changelogs",{"path":1782,"title":1783},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fsemantic-versioning-policy-for-cli-tools","A Semantic Versioning Policy for CLI Tools",{"path":1785,"title":1786},"\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":1788,"title":1789},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbuilding-wheels-and-sdists-for-python-clis","Building Wheels and sdists for Python CLIs",{"path":1791,"title":1792},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbundling-data-files-with-importlib-resources","Bundling Data Files with importlib.resources in CLIs",{"path":1794,"title":1795},"\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":1797,"title":1798},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution","Packaging Python CLIs for Distribution",{"path":1800,"title":1801},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Finstalling-and-distributing-clis-with-pipx","Installing and Distributing CLIs with pipx",{"path":1803,"title":1804},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Foptional-dependencies-and-extras-for-clis","Optional Dependencies and Extras for Python CLIs",{"path":1806,"title":1807},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fpublishing-a-python-cli-to-pypi","Publishing a Python CLI to PyPI",{"path":1809,"title":1810},"\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":1812,"title":1813},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fdynamic-versioning-with-poetry-plugins","Dynamic Versioning for a Poetry CLI from Git Tags",{"path":1815,"title":1816},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development","Poetry Workflows for CLI Development",{"path":1818,"title":1819},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fmanaging-poetry-lock-files-for-cli-tools","Managing Poetry Lock Files for CLI Tools",{"path":1821,"title":1822},"\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":1824,"title":1825},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-dependency-groups-for-cli-tooling","Poetry Dependency Groups for CLI Tooling",{"path":1827,"title":1828},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-entry-points-and-scripts-for-clis","Poetry Entry Points and Scripts for CLIs",{"path":1830,"title":1831},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpublishing-a-cli-with-poetry","Building and Publishing a Python CLI with Poetry",{"path":1833,"title":1834},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects","Pre-commit Hooks for CLI Projects",{"path":1836,"title":1837},"\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":1839,"title":1840},"\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":1842,"title":1843},"\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":1845,"title":1846},"\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":1848,"title":1849},"\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":1851,"title":1852},"\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":1854,"title":1855},"\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":1857,"title":1858},"\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":1860,"title":1861},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain","Securing the Supply Chain of a Python CLI",{"path":1863,"title":1864},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpinning-dependencies-with-hashes","Pinning a Python CLI’s Dependencies with Hashes",{"path":1866,"title":1867},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpublishing-attestations-and-verifying-releases","Publishing Attestations and Verifying Python CLI Releases",{"path":1869,"title":1870},"\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":1872,"title":1873},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management","uv for Python CLI Dependency Management",{"path":1057,"title":5},{"path":1876,"title":1877},"\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":1879,"title":1880},"\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":1882,"title":66},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-init-vs-poetry-init-for-cli-tools",{"path":1884,"title":1885},"\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":1887,"title":1888},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis","uv Workspaces for Multi-Package Python CLIs",{"path":1890,"title":1891},"\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":1893,"title":1894},"\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":1896,"title":1897},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices","Python CLI Env Isolation Best Practices",{"path":1899,"title":1900},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fisolating-cli-tools-from-project-dependencies","Isolating CLI Tools from Your Project’s Dependencies",{"path":1902,"title":1903},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fmanaging-virtual-environments-for-cross-platform-clis","Managing Python CLI Virtual Environments",{"path":1905,"title":1906},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fpinning-the-python-version-for-a-cli","Pinning the Python Version for a CLI",{"path":1908,"title":1909},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fsupporting-multiple-python-versions-with-nox","Supporting Multiple Python Versions with nox",1790967543063]