[{"data":1,"prerenderedAt":2405},["ShallowReactive",2],{"page-\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fupdating-generated-projects-with-copier-update\u002F":3,"content-directory":1562},{"id":4,"title":5,"body":6,"date":1547,"description":1548,"difficulty":1549,"draft":1550,"extension":1551,"meta":1552,"navigation":145,"path":1553,"seo":1554,"stem":1555,"tags":1556,"updated":1547,"__hash__":1561},"content\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fupdating-generated-projects-with-copier-update\u002Findex.md","Updating Generated CLI Projects with copier update",{"type":7,"value":8,"toc":1523},"minimark",[9,34,39,53,57,72,76,87,91,96,259,266,283,293,297,323,333,385,389,437,443,451,466,469,473,484,488,494,742,745,758,762,774,848,855,859,862,903,907,918,1410,1413,1417,1423,1427,1431,1441,1445,1448,1455,1465,1472,1486,1490,1519],[10,11,12,13,17,18,22,23,28,29,33],"p",{},"A project template pays for itself on day one: every new internal CLI starts with the same layout, the same Ruff and pytest configuration, the same CI workflow. The trouble starts on day ninety, when the template gains a better release workflow and a security fix to its pre-commit configuration — and the twelve CLIs generated from it do not. With Cookiecutter, generation is one-way; each project drifts from the moment it is created. ",[14,15,16],"strong",{},"Copier"," was designed for the opposite: it records which template version and which answers produced a project, and ",[19,20,21],"code",{},"copier update"," replays the template's changes since then onto the project, merging them with the project's own edits. This guide sets up a template so updates work, runs an update including the conflict case, and automates update pull requests across many projects. It belongs to the ",[24,25,27],"a",{"href":26},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002F","project scaffolding topic","; ",[24,30,32],{"href":31},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fcopier-vs-cookiecutter-for-cli-templates\u002F","Copier vs Cookiecutter for CLI templates"," explains the wider comparison.",[35,36,38],"h2",{"id":37},"prerequisites","Prerequisites",[40,41,42,50],"ul",{},[43,44,45,46,49],"li",{},"Copier 9 (",[19,47,48],{},"uv tool install copier","), and git.",[43,51,52],{},"A CLI template in its own git repository; the examples use a minimal one.",[35,54,56],{"id":55},"how-an-update-works","How an update works",[10,58,59,60,63,64,67,68,71],{},"Copier treats an update as a three-way merge. It regenerates the project from the ",[14,61,62],{},"old"," template version with the recorded answers, regenerates it from the ",[14,65,66],{},"new"," version with the same answers, computes the difference between the two, and applies that difference to the ",[14,69,70],{},"current"," project. Changes you made in the project are kept; changes the template made are applied; when both touched the same lines, you get a conflict to resolve.",[73,74],"inline-diagram",{"name":75},"copier-update-merge",[10,77,78,79,82,83,86],{},"That design has two requirements. The template must be a git repository with ",[14,80,81],{},"tags",", so Copier can check out the old and new versions. And the project must contain the ",[14,84,85],{},"answers file",", which records the template source, the version used and every answer.",[35,88,90],{"id":89},"the-recipe","The recipe",[92,93,95],"h3",{"id":94},"_1-make-the-template-updatable","1. Make the template updatable",[97,98,103],"pre",{"className":99,"code":100,"language":101,"meta":102,"style":102},"language-yaml shiki shiki-themes github-light github-dark","# copier.yml\n_subdirectory: template\n_answers_file: .copier-answers.yml\n\nproject_name:\n  type: str\n  help: Name of the CLI (as published)\npackage_name:\n  type: str\n  default: \"{{ project_name | lower | replace('-', '_') }}\"\npython_min:\n  type: str\n  default: \"3.11\"\n  choices: [\"3.10\", \"3.11\", \"3.12\"]\n","yaml","",[19,104,105,114,129,140,147,156,167,178,186,195,206,214,223,233],{"__ignoreMap":102},[106,107,110],"span",{"class":108,"line":109},"line",1,[106,111,113],{"class":112},"sJ8bj","# copier.yml\n",[106,115,117,121,125],{"class":108,"line":116},2,[106,118,120],{"class":119},"s9eBZ","_subdirectory",[106,122,124],{"class":123},"sVt8B",": ",[106,126,128],{"class":127},"sZZnC","template\n",[106,130,132,135,137],{"class":108,"line":131},3,[106,133,134],{"class":119},"_answers_file",[106,136,124],{"class":123},[106,138,139],{"class":127},".copier-answers.yml\n",[106,141,143],{"class":108,"line":142},4,[106,144,146],{"emptyLinePlaceholder":145},true,"\n",[106,148,150,153],{"class":108,"line":149},5,[106,151,152],{"class":119},"project_name",[106,154,155],{"class":123},":\n",[106,157,159,162,164],{"class":108,"line":158},6,[106,160,161],{"class":119},"  type",[106,163,124],{"class":123},[106,165,166],{"class":127},"str\n",[106,168,170,173,175],{"class":108,"line":169},7,[106,171,172],{"class":119},"  help",[106,174,124],{"class":123},[106,176,177],{"class":127},"Name of the CLI (as published)\n",[106,179,181,184],{"class":108,"line":180},8,[106,182,183],{"class":119},"package_name",[106,185,155],{"class":123},[106,187,189,191,193],{"class":108,"line":188},9,[106,190,161],{"class":119},[106,192,124],{"class":123},[106,194,166],{"class":127},[106,196,198,201,203],{"class":108,"line":197},10,[106,199,200],{"class":119},"  default",[106,202,124],{"class":123},[106,204,205],{"class":127},"\"{{ project_name | lower | replace('-', '_') }}\"\n",[106,207,209,212],{"class":108,"line":208},11,[106,210,211],{"class":119},"python_min",[106,213,155],{"class":123},[106,215,217,219,221],{"class":108,"line":216},12,[106,218,161],{"class":119},[106,220,124],{"class":123},[106,222,166],{"class":127},[106,224,226,228,230],{"class":108,"line":225},13,[106,227,200],{"class":119},[106,229,124],{"class":123},[106,231,232],{"class":127},"\"3.11\"\n",[106,234,236,239,242,245,248,251,253,256],{"class":108,"line":235},14,[106,237,238],{"class":119},"  choices",[106,240,241],{"class":123},": [",[106,243,244],{"class":127},"\"3.10\"",[106,246,247],{"class":123},", ",[106,249,250],{"class":127},"\"3.11\"",[106,252,247],{"class":123},[106,254,255],{"class":127},"\"3.12\"",[106,257,258],{"class":123},"]\n",[10,260,261,262,265],{},"The template's files live under ",[19,263,264],{},"template\u002F",", so repository files such as the template's own README and CI do not get copied into projects. One file in the template writes the answers back into every generated project:",[97,267,271],{"className":268,"code":269,"language":270,"meta":102,"style":102},"language-jinja shiki shiki-themes github-light github-dark","{# template\u002F{{_copier_conf.answers_file}}.jinja #}\n{{ _copier_answers|to_nice_yaml -}}\n","jinja",[19,272,273,278],{"__ignoreMap":102},[106,274,275],{"class":108,"line":109},[106,276,277],{},"{# template\u002F{{_copier_conf.answers_file}}.jinja #}\n",[106,279,280],{"class":108,"line":116},[106,281,282],{},"{{ _copier_answers|to_nice_yaml -}}\n",[10,284,285,286,247,289,292],{},"Tag releases of the template with semantic versions — ",[19,287,288],{},"v1.0.0",[19,290,291],{},"v1.1.0"," — exactly as you would a library. Copier updates to the newest tag by default, so untagged commits are invisible to updates, which gives you a natural \"release\" step for template changes.",[92,294,296],{"id":295},"_2-generate-a-project","2. Generate a project",[97,298,302],{"className":299,"code":300,"language":301,"meta":102,"style":102},"language-bash shiki shiki-themes github-light github-dark","copier copy --trust gh:acme\u002Fcli-template acme-deploy\n","bash",[19,303,304],{"__ignoreMap":102},[106,305,306,310,313,317,320],{"class":108,"line":109},[106,307,309],{"class":308},"sScJk","copier",[106,311,312],{"class":127}," copy",[106,314,316],{"class":315},"sj4cs"," --trust",[106,318,319],{"class":127}," gh:acme\u002Fcli-template",[106,321,322],{"class":127}," acme-deploy\n",[10,324,325,326,328,329,332],{},"Use a URL or an absolute path as the source; the answers file records it, and ",[19,327,21],{}," needs to find it again from inside the project. The generated ",[19,330,331],{},".copier-answers.yml"," looks like this and must be committed:",[97,334,336],{"className":99,"code":335,"language":101,"meta":102,"style":102},"_commit: v1.0.0\n_src_path: gh:acme\u002Fcli-template\npackage_name: acme_deploy\nproject_name: acme-deploy\npython_min: '3.11'\n",[19,337,338,348,358,367,376],{"__ignoreMap":102},[106,339,340,343,345],{"class":108,"line":109},[106,341,342],{"class":119},"_commit",[106,344,124],{"class":123},[106,346,347],{"class":127},"v1.0.0\n",[106,349,350,353,355],{"class":108,"line":116},[106,351,352],{"class":119},"_src_path",[106,354,124],{"class":123},[106,356,357],{"class":127},"gh:acme\u002Fcli-template\n",[106,359,360,362,364],{"class":108,"line":131},[106,361,183],{"class":119},[106,363,124],{"class":123},[106,365,366],{"class":127},"acme_deploy\n",[106,368,369,371,373],{"class":108,"line":142},[106,370,152],{"class":119},[106,372,124],{"class":123},[106,374,375],{"class":127},"acme-deploy\n",[106,377,378,380,382],{"class":108,"line":149},[106,379,211],{"class":119},[106,381,124],{"class":123},[106,383,384],{"class":127},"'3.11'\n",[92,386,388],{"id":387},"_3-update","3. Update",[97,390,392],{"className":299,"code":391,"language":301,"meta":102,"style":102},"cd acme-deploy\ngit status --short             # must be clean: copier refuses to update a dirty tree\ncopier update --trust          # newest tag; asks only about new questions\ngit diff                       # review what the template changed\n",[19,393,394,401,415,427],{"__ignoreMap":102},[106,395,396,399],{"class":108,"line":109},[106,397,398],{"class":315},"cd",[106,400,322],{"class":127},[106,402,403,406,409,412],{"class":108,"line":116},[106,404,405],{"class":308},"git",[106,407,408],{"class":127}," status",[106,410,411],{"class":315}," --short",[106,413,414],{"class":112},"             # must be clean: copier refuses to update a dirty tree\n",[106,416,417,419,422,424],{"class":108,"line":131},[106,418,309],{"class":308},[106,420,421],{"class":127}," update",[106,423,316],{"class":315},[106,425,426],{"class":112},"          # newest tag; asks only about new questions\n",[106,428,429,431,434],{"class":108,"line":142},[106,430,405],{"class":308},[106,432,433],{"class":127}," diff",[106,435,436],{"class":112},"                       # review what the template changed\n",[10,438,439,440,442],{},"When the template's change and the project's own edits do not overlap, the update applies cleanly and the answers file's ",[19,441,342],{}," moves to the new tag. When they do overlap, Copier writes inline conflict markers, just like a git merge:",[97,444,449],{"className":445,"code":447,"language":448,"meta":102},[446],"language-text","[project]\nname = \"acme-deploy\"\nrequires-python = \">=3.11\"\n\u003C\u003C\u003C\u003C\u003C\u003C\u003C before updating\n# my change\n=======\n\n[tool.ruff]\nline-length = 100\n>>>>>>> after updating\n","text",[19,450,447],{"__ignoreMap":102},[10,452,453,454,457,458,461,462,465],{},"Resolve them as you would any merge conflict, run the tests, and commit. ",[19,455,456],{},"git status"," shows conflicted files as unmerged, so they are hard to miss. If you prefer separate files, ",[19,459,460],{},"copier update --conflict rej"," writes ",[19,463,464],{},".rej"," files next to the originals instead.",[73,467],{"name":468},"copier-update-terminal",[92,470,472],{"id":471},"_4-change-an-answer","4. Change an answer",[10,474,475,476,479,480,483],{},"Answers are not frozen. ",[19,477,478],{},"copier update --data python_min=3.12"," (or re-answering when prompted with ",[19,481,482],{},"--ask python_min",") regenerates with the new value and applies the resulting differences, so bumping the minimum Python version across a project's template-managed files is a single update.",[35,485,487],{"id":486},"automating-updates-across-many-clis","Automating updates across many CLIs",[10,489,490,491,493],{},"With a dozen projects, nobody runs ",[19,492,21],{}," by hand. A scheduled workflow in each generated project can do it and open a pull request:",[97,495,497],{"className":99,"code":496,"language":101,"meta":102,"style":102},"# .github\u002Fworkflows\u002Ftemplate-update.yml (in each generated project)\nname: template-update\non:\n  schedule:\n    - cron: \"0 6 * * 1\"\n  workflow_dispatch:\n\npermissions:\n  contents: write\n  pull-requests: write\n\njobs:\n  update:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with:\n          fetch-depth: 0\n      - uses: astral-sh\u002Fsetup-uv@v6\n      - run: |\n          git config user.name \"template-bot\"\n          git config user.email \"template-bot@users.noreply.github.com\"\n          uvx copier update --trust --defaults --conflict rej\n      - uses: peter-evans\u002Fcreate-pull-request@v7\n        with:\n          branch: template-update\n          title: \"Update from project template\"\n          body: \"Automated `copier update`. Check for `.rej` files before merging.\"\n",[19,498,499,504,514,521,528,541,548,552,559,569,578,582,589,596,606,614,628,636,647,659,673,679,685,691,703,710,720,731],{"__ignoreMap":102},[106,500,501],{"class":108,"line":109},[106,502,503],{"class":112},"# .github\u002Fworkflows\u002Ftemplate-update.yml (in each generated project)\n",[106,505,506,509,511],{"class":108,"line":116},[106,507,508],{"class":119},"name",[106,510,124],{"class":123},[106,512,513],{"class":127},"template-update\n",[106,515,516,519],{"class":108,"line":131},[106,517,518],{"class":315},"on",[106,520,155],{"class":123},[106,522,523,526],{"class":108,"line":142},[106,524,525],{"class":119},"  schedule",[106,527,155],{"class":123},[106,529,530,533,536,538],{"class":108,"line":149},[106,531,532],{"class":123},"    - ",[106,534,535],{"class":119},"cron",[106,537,124],{"class":123},[106,539,540],{"class":127},"\"0 6 * * 1\"\n",[106,542,543,546],{"class":108,"line":158},[106,544,545],{"class":119},"  workflow_dispatch",[106,547,155],{"class":123},[106,549,550],{"class":108,"line":169},[106,551,146],{"emptyLinePlaceholder":145},[106,553,554,557],{"class":108,"line":180},[106,555,556],{"class":119},"permissions",[106,558,155],{"class":123},[106,560,561,564,566],{"class":108,"line":188},[106,562,563],{"class":119},"  contents",[106,565,124],{"class":123},[106,567,568],{"class":127},"write\n",[106,570,571,574,576],{"class":108,"line":197},[106,572,573],{"class":119},"  pull-requests",[106,575,124],{"class":123},[106,577,568],{"class":127},[106,579,580],{"class":108,"line":208},[106,581,146],{"emptyLinePlaceholder":145},[106,583,584,587],{"class":108,"line":216},[106,585,586],{"class":119},"jobs",[106,588,155],{"class":123},[106,590,591,594],{"class":108,"line":225},[106,592,593],{"class":119},"  update",[106,595,155],{"class":123},[106,597,598,601,603],{"class":108,"line":235},[106,599,600],{"class":119},"    runs-on",[106,602,124],{"class":123},[106,604,605],{"class":127},"ubuntu-latest\n",[106,607,609,612],{"class":108,"line":608},15,[106,610,611],{"class":119},"    steps",[106,613,155],{"class":123},[106,615,617,620,623,625],{"class":108,"line":616},16,[106,618,619],{"class":123},"      - ",[106,621,622],{"class":119},"uses",[106,624,124],{"class":123},[106,626,627],{"class":127},"actions\u002Fcheckout@v4\n",[106,629,631,634],{"class":108,"line":630},17,[106,632,633],{"class":119},"        with",[106,635,155],{"class":123},[106,637,639,642,644],{"class":108,"line":638},18,[106,640,641],{"class":119},"          fetch-depth",[106,643,124],{"class":123},[106,645,646],{"class":315},"0\n",[106,648,650,652,654,656],{"class":108,"line":649},19,[106,651,619],{"class":123},[106,653,622],{"class":119},[106,655,124],{"class":123},[106,657,658],{"class":127},"astral-sh\u002Fsetup-uv@v6\n",[106,660,662,664,667,669],{"class":108,"line":661},20,[106,663,619],{"class":123},[106,665,666],{"class":119},"run",[106,668,124],{"class":123},[106,670,672],{"class":671},"szBVR","|\n",[106,674,676],{"class":108,"line":675},21,[106,677,678],{"class":127},"          git config user.name \"template-bot\"\n",[106,680,682],{"class":108,"line":681},22,[106,683,684],{"class":127},"          git config user.email \"template-bot@users.noreply.github.com\"\n",[106,686,688],{"class":108,"line":687},23,[106,689,690],{"class":127},"          uvx copier update --trust --defaults --conflict rej\n",[106,692,694,696,698,700],{"class":108,"line":693},24,[106,695,619],{"class":123},[106,697,622],{"class":119},[106,699,124],{"class":123},[106,701,702],{"class":127},"peter-evans\u002Fcreate-pull-request@v7\n",[106,704,706,708],{"class":108,"line":705},25,[106,707,633],{"class":119},[106,709,155],{"class":123},[106,711,713,716,718],{"class":108,"line":712},26,[106,714,715],{"class":119},"          branch",[106,717,124],{"class":123},[106,719,513],{"class":127},[106,721,723,726,728],{"class":108,"line":722},27,[106,724,725],{"class":119},"          title",[106,727,124],{"class":123},[106,729,730],{"class":127},"\"Update from project template\"\n",[106,732,734,737,739],{"class":108,"line":733},28,[106,735,736],{"class":119},"          body",[106,738,124],{"class":123},[106,740,741],{"class":127},"\"Automated `copier update`. Check for `.rej` files before merging.\"\n",[73,743],{"name":744},"copier-update-fleet",[10,746,747,750,751,754,755,757],{},[19,748,749],{},"--defaults"," accepts default answers for any new questions, so the job never waits for input; ",[19,752,753],{},"--conflict rej"," keeps conflicts out of the code so the pull request's diff stays readable, with ",[19,756,464],{}," files flagging what needs a human. Renovate also understands Copier answer files and can open the same pull requests across an organisation from one configuration.",[35,759,761],{"id":760},"migrations-between-template-versions","Migrations between template versions",[10,763,764,765,769,770,773],{},"Some template changes cannot be expressed as a diff: renaming a question, moving a file whose content the project has heavily edited, or deleting a tool configuration that projects should migrate away from. Copier supports ",[766,767,768],"em",{},"migrations"," in ",[19,771,772],{},"copier.yml"," — commands that run before or after updating across a given template version:",[97,775,777],{"className":99,"code":776,"language":101,"meta":102,"style":102},"_migrations:\n  - version: v2.0.0\n    before:\n      - \"{{ _copier_python }} -c \\\"import pathlib; p = pathlib.Path('setup.cfg'); p.exists() and p.unlink()\\\"\"\n  - version: v2.0.0\n    after:\n      - \"{{ _copier_python }} -m pip --version\"\n",[19,778,779,786,799,806,824,834,841],{"__ignoreMap":102},[106,780,781,784],{"class":108,"line":109},[106,782,783],{"class":119},"_migrations",[106,785,155],{"class":123},[106,787,788,791,794,796],{"class":108,"line":116},[106,789,790],{"class":123},"  - ",[106,792,793],{"class":119},"version",[106,795,124],{"class":123},[106,797,798],{"class":127},"v2.0.0\n",[106,800,801,804],{"class":108,"line":131},[106,802,803],{"class":119},"    before",[106,805,155],{"class":123},[106,807,808,810,813,816,819,821],{"class":108,"line":142},[106,809,619],{"class":123},[106,811,812],{"class":127},"\"{{ _copier_python }} -c ",[106,814,815],{"class":315},"\\\"",[106,817,818],{"class":127},"import pathlib; p = pathlib.Path('setup.cfg'); p.exists() and p.unlink()",[106,820,815],{"class":315},[106,822,823],{"class":127},"\"\n",[106,825,826,828,830,832],{"class":108,"line":149},[106,827,790],{"class":123},[106,829,793],{"class":119},[106,831,124],{"class":123},[106,833,798],{"class":127},[106,835,836,839],{"class":108,"line":158},[106,837,838],{"class":119},"    after",[106,840,155],{"class":123},[106,842,843,845],{"class":108,"line":169},[106,844,619],{"class":123},[106,846,847],{"class":127},"\"{{ _copier_python }} -m pip --version\"\n",[10,849,850,851,854],{},"Migrations are code that runs in every project being updated, so they require ",[19,852,853],{},"--trust"," and deserve the same review as any script with write access to a repository. Keep them small, idempotent and safe to run on a project that has already been fixed by hand. For renamed questions, prefer keeping the old name with a new default for one major version, then removing it — answers files from old projects keep working during the transition. And always describe migrations in the template changelog: they are the part of an update most likely to surprise someone reviewing the pull request.",[35,856,858],{"id":857},"ux-considerations","UX considerations",[10,860,861],{},"The users here are the maintainers of generated projects, who did not write the template:",[40,863,864,870,876,886,892],{},[43,865,866,869],{},[14,867,868],{},"Write a template changelog."," An update pull request is far easier to review when the template's release notes explain why the CI workflow changed.",[43,871,872,875],{},[14,873,874],{},"Keep template changes small and tagged often."," Many small updates conflict less than one large one a year later.",[43,877,878,881,882,885],{},[14,879,880],{},"Separate \"owned by the template\" from \"owned by the project\"."," Files the project should customise freely (the README body, the command code) are better generated once and excluded from updates with ",[19,883,884],{},"_skip_if_exists",", so updates never fight with them.",[43,887,888,891],{},[14,889,890],{},"Do not make every value a question."," Each answer is a dimension the template must support forever; prefer conventions over options.",[43,893,894,897,898,902],{},[14,895,896],{},"Test the template",", including updates from older tags, as in ",[24,899,901],{"href":900},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftesting-a-project-template-with-pytest\u002F","testing a project template with pytest",".",[35,904,906],{"id":905},"testing-the-behaviour","Testing the behaviour",[10,908,909,910,913,914,917],{},"Copier exposes ",[19,911,912],{},"run_copy"," and ",[19,915,916],{},"run_update"," for Python, which makes it possible to test the update path of a template in its own CI: generate from the previous tag, make a typical local edit, update to the working tree, and check the result:",[97,919,923],{"className":920,"code":921,"language":922,"meta":102,"style":102},"language-python shiki shiki-themes github-light github-dark","# tests\u002Ftest_update.py\nimport subprocess\nfrom pathlib import Path\n\nfrom copier import run_copy, run_update\n\nTEMPLATE = Path(__file__).resolve().parents[1]\n\n\ndef git(*args, cwd):\n    subprocess.run([\"git\", *args], cwd=cwd, check=True, capture_output=True,\n                   env={\"GIT_AUTHOR_NAME\": \"t\", \"GIT_AUTHOR_EMAIL\": \"t@example.com\",\n                        \"GIT_COMMITTER_NAME\": \"t\", \"GIT_COMMITTER_EMAIL\": \"t@example.com\",\n                        \"PATH\": \"\u002Fusr\u002Fbin:\u002Fbin\"})\n\n\ndef test_update_from_previous_release(tmp_path):\n    project = tmp_path \u002F \"proj\"\n    run_copy(str(TEMPLATE), project, data={\"project_name\": \"acme-deploy\"},\n             vcs_ref=\"v1.0.0\", defaults=True, unsafe=True, quiet=True)\n    git(\"init\", \"-q\", \"-b\", \"main\", cwd=project)\n    git(\"add\", \"-A\", cwd=project)\n    git(\"commit\", \"-qm\", \"generated\", cwd=project)\n\n    run_update(project, defaults=True, unsafe=True, quiet=True, overwrite=True)\n\n    answers = (project \u002F \".copier-answers.yml\").read_text()\n    assert \"_commit: v1.0.0\" not in answers\n    assert \"[tool.ruff]\" in (project \u002F \"pyproject.toml\").read_text()\n","python",[19,924,925,930,938,951,955,967,971,993,997,1001,1018,1063,1093,1113,1126,1130,1134,1144,1160,1193,1233,1265,1285,1310,1314,1352,1356,1374,1391],{"__ignoreMap":102},[106,926,927],{"class":108,"line":109},[106,928,929],{"class":112},"# tests\u002Ftest_update.py\n",[106,931,932,935],{"class":108,"line":116},[106,933,934],{"class":671},"import",[106,936,937],{"class":123}," subprocess\n",[106,939,940,943,946,948],{"class":108,"line":131},[106,941,942],{"class":671},"from",[106,944,945],{"class":123}," pathlib ",[106,947,934],{"class":671},[106,949,950],{"class":123}," Path\n",[106,952,953],{"class":108,"line":142},[106,954,146],{"emptyLinePlaceholder":145},[106,956,957,959,962,964],{"class":108,"line":149},[106,958,942],{"class":671},[106,960,961],{"class":123}," copier ",[106,963,934],{"class":671},[106,965,966],{"class":123}," run_copy, run_update\n",[106,968,969],{"class":108,"line":158},[106,970,146],{"emptyLinePlaceholder":145},[106,972,973,976,979,982,985,988,991],{"class":108,"line":169},[106,974,975],{"class":315},"TEMPLATE",[106,977,978],{"class":671}," =",[106,980,981],{"class":123}," Path(",[106,983,984],{"class":315},"__file__",[106,986,987],{"class":123},").resolve().parents[",[106,989,990],{"class":315},"1",[106,992,258],{"class":123},[106,994,995],{"class":108,"line":180},[106,996,146],{"emptyLinePlaceholder":145},[106,998,999],{"class":108,"line":188},[106,1000,146],{"emptyLinePlaceholder":145},[106,1002,1003,1006,1009,1012,1015],{"class":108,"line":197},[106,1004,1005],{"class":671},"def",[106,1007,1008],{"class":308}," git",[106,1010,1011],{"class":123},"(",[106,1013,1014],{"class":671},"*",[106,1016,1017],{"class":123},"args, cwd):\n",[106,1019,1020,1023,1026,1028,1030,1033,1037,1040,1043,1046,1048,1051,1053,1056,1058,1060],{"class":108,"line":208},[106,1021,1022],{"class":123},"    subprocess.run([",[106,1024,1025],{"class":127},"\"git\"",[106,1027,247],{"class":123},[106,1029,1014],{"class":671},[106,1031,1032],{"class":123},"args], ",[106,1034,1036],{"class":1035},"s4XuR","cwd",[106,1038,1039],{"class":671},"=",[106,1041,1042],{"class":123},"cwd, ",[106,1044,1045],{"class":1035},"check",[106,1047,1039],{"class":671},[106,1049,1050],{"class":315},"True",[106,1052,247],{"class":123},[106,1054,1055],{"class":1035},"capture_output",[106,1057,1039],{"class":671},[106,1059,1050],{"class":315},[106,1061,1062],{"class":123},",\n",[106,1064,1065,1068,1070,1073,1076,1078,1081,1083,1086,1088,1091],{"class":108,"line":216},[106,1066,1067],{"class":1035},"                   env",[106,1069,1039],{"class":671},[106,1071,1072],{"class":123},"{",[106,1074,1075],{"class":127},"\"GIT_AUTHOR_NAME\"",[106,1077,124],{"class":123},[106,1079,1080],{"class":127},"\"t\"",[106,1082,247],{"class":123},[106,1084,1085],{"class":127},"\"GIT_AUTHOR_EMAIL\"",[106,1087,124],{"class":123},[106,1089,1090],{"class":127},"\"t@example.com\"",[106,1092,1062],{"class":123},[106,1094,1095,1098,1100,1102,1104,1107,1109,1111],{"class":108,"line":225},[106,1096,1097],{"class":127},"                        \"GIT_COMMITTER_NAME\"",[106,1099,124],{"class":123},[106,1101,1080],{"class":127},[106,1103,247],{"class":123},[106,1105,1106],{"class":127},"\"GIT_COMMITTER_EMAIL\"",[106,1108,124],{"class":123},[106,1110,1090],{"class":127},[106,1112,1062],{"class":123},[106,1114,1115,1118,1120,1123],{"class":108,"line":235},[106,1116,1117],{"class":127},"                        \"PATH\"",[106,1119,124],{"class":123},[106,1121,1122],{"class":127},"\"\u002Fusr\u002Fbin:\u002Fbin\"",[106,1124,1125],{"class":123},"})\n",[106,1127,1128],{"class":108,"line":608},[106,1129,146],{"emptyLinePlaceholder":145},[106,1131,1132],{"class":108,"line":616},[106,1133,146],{"emptyLinePlaceholder":145},[106,1135,1136,1138,1141],{"class":108,"line":630},[106,1137,1005],{"class":671},[106,1139,1140],{"class":308}," test_update_from_previous_release",[106,1142,1143],{"class":123},"(tmp_path):\n",[106,1145,1146,1149,1151,1154,1157],{"class":108,"line":638},[106,1147,1148],{"class":123},"    project ",[106,1150,1039],{"class":671},[106,1152,1153],{"class":123}," tmp_path ",[106,1155,1156],{"class":671},"\u002F",[106,1158,1159],{"class":127}," \"proj\"\n",[106,1161,1162,1165,1168,1170,1172,1175,1178,1180,1182,1185,1187,1190],{"class":108,"line":649},[106,1163,1164],{"class":123},"    run_copy(",[106,1166,1167],{"class":315},"str",[106,1169,1011],{"class":123},[106,1171,975],{"class":315},[106,1173,1174],{"class":123},"), project, ",[106,1176,1177],{"class":1035},"data",[106,1179,1039],{"class":671},[106,1181,1072],{"class":123},[106,1183,1184],{"class":127},"\"project_name\"",[106,1186,124],{"class":123},[106,1188,1189],{"class":127},"\"acme-deploy\"",[106,1191,1192],{"class":123},"},\n",[106,1194,1195,1198,1200,1203,1205,1208,1210,1212,1214,1217,1219,1221,1223,1226,1228,1230],{"class":108,"line":661},[106,1196,1197],{"class":1035},"             vcs_ref",[106,1199,1039],{"class":671},[106,1201,1202],{"class":127},"\"v1.0.0\"",[106,1204,247],{"class":123},[106,1206,1207],{"class":1035},"defaults",[106,1209,1039],{"class":671},[106,1211,1050],{"class":315},[106,1213,247],{"class":123},[106,1215,1216],{"class":1035},"unsafe",[106,1218,1039],{"class":671},[106,1220,1050],{"class":315},[106,1222,247],{"class":123},[106,1224,1225],{"class":1035},"quiet",[106,1227,1039],{"class":671},[106,1229,1050],{"class":315},[106,1231,1232],{"class":123},")\n",[106,1234,1235,1238,1241,1243,1246,1248,1251,1253,1256,1258,1260,1262],{"class":108,"line":675},[106,1236,1237],{"class":123},"    git(",[106,1239,1240],{"class":127},"\"init\"",[106,1242,247],{"class":123},[106,1244,1245],{"class":127},"\"-q\"",[106,1247,247],{"class":123},[106,1249,1250],{"class":127},"\"-b\"",[106,1252,247],{"class":123},[106,1254,1255],{"class":127},"\"main\"",[106,1257,247],{"class":123},[106,1259,1036],{"class":1035},[106,1261,1039],{"class":671},[106,1263,1264],{"class":123},"project)\n",[106,1266,1267,1269,1272,1274,1277,1279,1281,1283],{"class":108,"line":681},[106,1268,1237],{"class":123},[106,1270,1271],{"class":127},"\"add\"",[106,1273,247],{"class":123},[106,1275,1276],{"class":127},"\"-A\"",[106,1278,247],{"class":123},[106,1280,1036],{"class":1035},[106,1282,1039],{"class":671},[106,1284,1264],{"class":123},[106,1286,1287,1289,1292,1294,1297,1299,1302,1304,1306,1308],{"class":108,"line":687},[106,1288,1237],{"class":123},[106,1290,1291],{"class":127},"\"commit\"",[106,1293,247],{"class":123},[106,1295,1296],{"class":127},"\"-qm\"",[106,1298,247],{"class":123},[106,1300,1301],{"class":127},"\"generated\"",[106,1303,247],{"class":123},[106,1305,1036],{"class":1035},[106,1307,1039],{"class":671},[106,1309,1264],{"class":123},[106,1311,1312],{"class":108,"line":693},[106,1313,146],{"emptyLinePlaceholder":145},[106,1315,1316,1319,1321,1323,1325,1327,1329,1331,1333,1335,1337,1339,1341,1343,1346,1348,1350],{"class":108,"line":705},[106,1317,1318],{"class":123},"    run_update(project, ",[106,1320,1207],{"class":1035},[106,1322,1039],{"class":671},[106,1324,1050],{"class":315},[106,1326,247],{"class":123},[106,1328,1216],{"class":1035},[106,1330,1039],{"class":671},[106,1332,1050],{"class":315},[106,1334,247],{"class":123},[106,1336,1225],{"class":1035},[106,1338,1039],{"class":671},[106,1340,1050],{"class":315},[106,1342,247],{"class":123},[106,1344,1345],{"class":1035},"overwrite",[106,1347,1039],{"class":671},[106,1349,1050],{"class":315},[106,1351,1232],{"class":123},[106,1353,1354],{"class":108,"line":712},[106,1355,146],{"emptyLinePlaceholder":145},[106,1357,1358,1361,1363,1366,1368,1371],{"class":108,"line":722},[106,1359,1360],{"class":123},"    answers ",[106,1362,1039],{"class":671},[106,1364,1365],{"class":123}," (project ",[106,1367,1156],{"class":671},[106,1369,1370],{"class":127}," \".copier-answers.yml\"",[106,1372,1373],{"class":123},").read_text()\n",[106,1375,1376,1379,1382,1385,1388],{"class":108,"line":733},[106,1377,1378],{"class":671},"    assert",[106,1380,1381],{"class":127}," \"_commit: v1.0.0\"",[106,1383,1384],{"class":671}," not",[106,1386,1387],{"class":671}," in",[106,1389,1390],{"class":123}," answers\n",[106,1392,1394,1396,1399,1401,1403,1405,1408],{"class":108,"line":1393},29,[106,1395,1378],{"class":671},[106,1397,1398],{"class":127}," \"[tool.ruff]\"",[106,1400,1387],{"class":671},[106,1402,1365],{"class":123},[106,1404,1156],{"class":671},[106,1406,1407],{"class":127}," \"pyproject.toml\"",[106,1409,1373],{"class":123},[10,1411,1412],{},"Run it in the template's CI against the last two or three tags, so a template change that breaks updates for existing projects fails before it is released.",[35,1414,1416],{"id":1415},"conclusion","Conclusion",[10,1418,1419,1420,1422],{},"Copier turns a project template from a one-time starting point into a maintained dependency. Keep the template in git with semantic-version tags and an answers file template, generate projects from a URL, commit the answers file, and run ",[19,1421,21],{}," — by hand or from a weekly pull-request workflow — to replay template changes onto each project as a three-way merge. Small, tagged template releases with a changelog keep those updates easy to review.",[35,1424,1426],{"id":1425},"frequently-asked-questions","Frequently asked questions",[92,1428,1430],{"id":1429},"can-i-update-a-project-that-was-generated-with-cookiecutter","Can I update a project that was generated with Cookiecutter?",[10,1432,1433,1434,1437,1438,1440],{},"Not directly — Cookiecutter records no template version. You can migrate by recreating the project with Copier from the template version closest to the original (with ",[19,1435,1436],{},"copier copy --vcs-ref","), committing the answers file, and from then on using ",[19,1439,21],{},". The first update will be noisy; later ones will not.",[92,1442,1444],{"id":1443},"what-if-the-template-renames-a-file","What if the template renames a file?",[10,1446,1447],{},"Copier applies the rename as part of the diff, so the project's copy moves too — including any local edits, if they do not conflict. Mention renames in the template changelog, because they are the changes reviewers most often misread.",[92,1449,1451,1452,1454],{"id":1450},"why-does-copier-update-refuse-to-run","Why does ",[19,1453,21],{}," refuse to run?",[10,1456,1457,1458,1460,1461,1464],{},"The usual reasons: uncommitted changes (commit or stash first), a relative ",[19,1459,352],{}," that cannot be resolved from the project directory, or a template without tags. ",[19,1462,1463],{},"copier update --vcs-ref HEAD"," can update to an untagged commit for testing, but releases should be tagged.",[92,1466,1468,1469,1471],{"id":1467},"do-i-need-trust","Do I need ",[19,1470,853],{},"?",[10,1473,1474,1475,1477,1478,1481,1482,902],{},"Only if the template runs tasks or uses Jinja extensions — Copier refuses those from untrusted sources by default. For your own organisation's template, ",[19,1476,853],{}," is fine; for a third-party template, read its ",[19,1479,1480],{},"_tasks"," first, just as you would review ",[24,1483,1485],{"href":1484},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fpost-generation-hooks-in-cli-templates\u002F","post-generation hooks",[35,1487,1489],{"id":1488},"related","Related",[40,1491,1492,1498,1502,1507,1513],{},[43,1493,1494,1495],{},"Up: ",[24,1496,1497],{"href":26},"CLI project scaffolding with cookiecutter",[43,1499,1500],{},[24,1501,32],{"href":31},[43,1503,1504],{},[24,1505,1506],{"href":900},"Testing a project template with pytest",[43,1508,1509],{},[24,1510,1512],{"href":1511},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftemplate-variables-and-conditional-files\u002F","Template variables and conditional files",[43,1514,1515],{},[24,1516,1518],{"href":1517},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects\u002Fsetting-up-pre-commit-for-python-cli-repos\u002F","Setting up pre-commit for Python CLI repos",[1520,1521,1522],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}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 .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}",{"title":102,"searchDepth":116,"depth":116,"links":1524},[1525,1526,1527,1533,1534,1535,1536,1537,1538,1546],{"id":37,"depth":116,"text":38},{"id":55,"depth":116,"text":56},{"id":89,"depth":116,"text":90,"children":1528},[1529,1530,1531,1532],{"id":94,"depth":131,"text":95},{"id":295,"depth":131,"text":296},{"id":387,"depth":131,"text":388},{"id":471,"depth":131,"text":472},{"id":486,"depth":116,"text":487},{"id":760,"depth":116,"text":761},{"id":857,"depth":116,"text":858},{"id":905,"depth":116,"text":906},{"id":1415,"depth":116,"text":1416},{"id":1425,"depth":116,"text":1426,"children":1539},[1540,1541,1542,1544],{"id":1429,"depth":131,"text":1430},{"id":1443,"depth":131,"text":1444},{"id":1450,"depth":131,"text":1543},"Why does copier update refuse to run?",{"id":1467,"depth":131,"text":1545},"Do I need --trust?",{"id":1488,"depth":116,"text":1489},"2026-10-02","Keep CLIs generated from a template current: tag the template, record answers, run copier update, resolve conflicts and automate update pull requests.","intermediate",false,"md",{},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fupdating-generated-projects-with-copier-update",{"title":5,"description":1548},"project-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fupdating-generated-projects-with-copier-update\u002Findex",[309,1557,1558,1559,1560],"templates","scaffolding","maintenance","automation","h2NpsZXPmscyv5CjksOQrvniGl_uVJqI8GjzGNylSDE",[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,1982,1985,1988,1991,1994,1997,2000,2003,2006,2009,2012,2015,2018,2021,2024,2027,2030,2033,2036,2039,2042,2045,2048,2051,2054,2057,2060,2063,2066,2069,2072,2075,2078,2081,2084,2087,2090,2093,2096,2099,2102,2105,2108,2111,2114,2117,2120,2123,2126,2129,2132,2135,2138,2141,2144,2147,2150,2153,2156,2159,2162,2165,2168,2171,2174,2177,2180,2183,2186,2189,2192,2195,2198,2201,2204,2207,2210,2211,2214,2217,2220,2223,2226,2229,2232,2235,2238,2241,2244,2247,2250,2253,2256,2259,2262,2265,2268,2271,2274,2277,2280,2283,2286,2289,2292,2295,2298,2301,2304,2307,2310,2313,2316,2319,2322,2325,2328,2331,2334,2336,2339,2342,2345,2348,2351,2354,2357,2360,2363,2366,2369,2372,2375,2378,2381,2384,2387,2390,2393,2396,2399,2402],{"path":1564,"title":1565},"\u002Fabout","About Python CLI Toolcraft",{"path":1567,"title":1568},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies","Advanced Argument Validation Strategies",{"path":1570,"title":1571},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fparsing-nested-json-arguments-in-python-clis","Parsing Nested JSON Args in Python CLIs",{"path":1573,"title":1574},"\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":1576,"title":1577},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-dependent-and-conflicting-options","Validating Dependent and Conflicting CLI Options",{"path":1579,"title":1580},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-file-and-directory-paths-in-clis","Validating File and Directory Paths in CLIs",{"path":1582,"title":1583},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-urls-hosts-and-ports","Validating URLs, Hosts and Ports in Python CLI Arguments",{"path":1585,"title":1586},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fwriting-custom-click-parameter-types","Writing Custom Click Parameter Types",{"path":1588,"title":1589},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fbrowsing-records-with-a-textual-datatable","Browsing Records with a Textual DataTable Picker",{"path":1591,"title":1592},"\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":1594,"title":1595},"\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":1597,"title":1598},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual","Building Terminal UIs with Textual for Python CLIs",{"path":1600,"title":1601},"\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":1603,"title":1604},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fstyling-textual-apps-with-tcss","Styling Textual Apps with TCSS",{"path":1606,"title":1607},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Ftesting-textual-apps-with-pilot","Testing Textual Apps with Pilot",{"path":1609,"title":1610},"\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":1612,"title":1613},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fdocumenting-environment-variables-in-help","Documenting Environment Variables in CLI Help",{"path":1615,"title":1616},"\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":1618,"title":1619},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation","CLI Help Output and Documentation",{"path":1621,"title":1622},"\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":1624,"title":1625},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fversioning-and-deprecating-cli-flags","Versioning and Deprecating CLI Flags",{"path":1627,"title":1628},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fwriting-help-text-users-actually-read","Writing Help Text Users Actually Read",{"path":1630,"title":1631},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fadapting-output-to-terminal-width","Adapting Python CLI Output to Terminal Width",{"path":1633,"title":1634},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fdetecting-ci-environments-and-non-interactive-shells","Detecting CI Environments and Non-Interactive Shells",{"path":1636,"title":1637},"\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":1639,"title":1640},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fhandling-ansi-escape-codes-on-windows-consoles","Handling ANSI Escape Codes on Windows Consoles",{"path":1642,"title":1643},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility","Cross-Platform Terminal Compatibility for Python CLIs",{"path":1645,"title":1646},"\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":1648,"title":1649},"\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":1651,"title":1652},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fchoosing-exit-codes-for-cli-tools","Choosing Exit Codes for CLI Tools",{"path":1654,"title":1655},"\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":1657,"title":1658},"\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":1660,"title":1661},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Ffriendly-error-messages-and-tracebacks","Friendly Error Messages and Tracebacks",{"path":1663,"title":1664},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fhandling-keyboard-interrupt-cleanly","Handling Keyboard Interrupt Cleanly",{"path":1666,"title":1667},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes","Error Handling and Exit Codes for CLIs",{"path":1669,"title":1670},"\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":1672,"title":1673},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fwriting-crash-reports-users-can-send","Writing Crash Reports Users Can Send",{"path":1675,"title":1676},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Fconfig-precedence-flags-env-files-defaults","Config Precedence: Flags, Env, Files, Defaults",{"path":1678,"title":1679},"\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":1681,"title":1682},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars","Handling Config Files and Env Vars in CLIs",{"path":1684,"title":1685},"\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":1687,"title":1688},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Freading-toml-config-with-tomllib","Reading TOML Config with tomllib in Python CLIs",{"path":1690,"title":1691},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Ftyped-settings-with-pydantic-settings","Typed Settings with pydantic-settings in Python CLIs",{"path":1693,"title":1694},"\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":1696,"title":1697},"\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":1699,"title":1700},"\u002Fadvanced-input-parsing-user-experience","Advanced Input Parsing for Python CLIs",{"path":1702,"title":1703},"\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":1705,"title":1706},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Fbuilding-interactive-prompts-and-menus","Building Interactive Prompts and Menus in Python CLIs",{"path":1708,"title":1709},"\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":1711,"title":1712},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich","Interactive Terminal UI with Rich",{"path":1714,"title":1715},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Flive-dashboards-with-rich-live","Live Dashboards with Rich Live in Python CLIs",{"path":1717,"title":1718},"\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":1720,"title":1721},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Frendering-tables-and-json-with-rich","Rendering Tables and JSON with Rich",{"path":1723,"title":1724},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Ftheming-rich-output-consistently","Theming Rich Output Consistently in Python CLIs",{"path":1726,"title":1727},"\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":1729,"title":1730},"\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":1732,"title":1733},"\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":1735,"title":1736},"\u002Fadvanced-input-parsing-user-experience\u002Foutput-formats-for-data-clis","Output Formats for Data-Heavy Python CLIs",{"path":1738,"title":1739},"\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":1741,"title":1742},"\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":1744,"title":1745},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fargcomplete-for-argparse-clis","Tab Completion for argparse CLIs with argcomplete",{"path":1747,"title":1748},"\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":1750,"title":1751},"\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":1753,"title":1754},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis","Shell Completion for Python CLIs",{"path":1756,"title":1757},"\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":1759,"title":1760},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fshipping-completion-scripts-with-packages","Shipping Shell Completion Scripts with a Python CLI",{"path":1762,"title":1763},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Ftesting-shell-completion-in-python-clis","Testing Shell Completion in Python CLIs",{"path":1765,"title":1766},"\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":1768,"title":1769},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fadding-verbose-and-quiet-logging-flags","Adding Verbose and Quiet Logging Flags",{"path":1771,"title":1772},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps","Structured Logging for CLI Apps",{"path":1774,"title":1775},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Flogging-with-structlog-in-a-cli","Logging with structlog in a Python CLI",{"path":1777,"title":1778},"\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":1780,"title":1781},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fstructured-json-logging-in-python-clis","Structured JSON Logging in Python CLIs",{"path":1783,"title":1784},"\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":1786,"title":1787},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fdetecting-tty-and-adapting-output","Detecting a TTY and Adapting Output",{"path":1789,"title":1790},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Femitting-json-output-for-scripting","Emitting JSON Output for Scripting",{"path":1792,"title":1793},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fhandling-broken-pipe-and-sigpipe","Handling Broken Pipe and SIGPIPE",{"path":1795,"title":1796},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes","Working with stdin, stdout and Pipes",{"path":1798,"title":1799},"\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":1801,"title":1802},"\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":1804,"title":1805},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Freading-piped-input-in-python-clis","Reading Piped Input in Python CLIs",{"path":1807,"title":1808},"\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":1810,"title":1811},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fdownloading-files-with-progress-in-python","Downloading Files with Progress in Python CLIs",{"path":1813,"title":1814},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis","Calling HTTP APIs from Python CLIs",{"path":1816,"title":1817},"\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":1819,"title":1820},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Foauth-device-flow-login-for-clis","OAuth Device Flow Login for Python CLIs",{"path":1822,"title":1823},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fpaginating-api-results-in-a-cli","Paginating API Results in a Python CLI",{"path":1825,"title":1826},"\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":1828,"title":1829},"\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":1831,"title":1832},"\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":1834,"title":1835},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis","Concurrency and Async in Python CLIs",{"path":1837,"title":1838},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fmultiprocessing-for-cpu-bound-cli-tasks","Multiprocessing for CPU-Bound CLI Tasks",{"path":1840,"title":1841},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fparallelising-cli-work-with-thread-pools","Parallelising CLI Work with Thread Pools",{"path":1843,"title":1844},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Frate-limiting-concurrent-requests-in-clis","Rate-Limiting Concurrent Requests in Python CLIs",{"path":1846,"title":1847},"\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":1849,"title":1850},"\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":1852,"title":1853},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fstructured-concurrency-with-taskgroups-in-clis","Structured Concurrency with TaskGroups in Python CLIs",{"path":1855,"title":1856},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fcross-platform-paths-with-pathlib","Cross-Platform Paths with pathlib in CLIs",{"path":1858,"title":1859},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Ffile-locking-for-concurrent-cli-runs","File Locking for Concurrent CLI Runs in Python",{"path":1861,"title":1862},"\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":1864,"title":1865},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes","Filesystem Paths and Atomic Writes for CLIs",{"path":1867,"title":1868},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fsafe-temporary-files-and-directories","Safe Temporary Files and Directories in CLIs",{"path":1870,"title":1871},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fstoring-app-data-with-platformdirs","Storing CLI App Data with platformdirs",{"path":1873,"title":1874},"\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":1876,"title":1877},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fwriting-files-atomically-in-python-clis","Writing Files Atomically in Python CLIs",{"path":1879,"title":1880},"\u002Fcli-runtime-systems-integration","CLI Runtime & Systems Integration for Python",{"path":1882,"title":1883},"\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":1885,"title":1886},"\u002Fcli-runtime-systems-integration\u002Flocal-state-and-sqlite-in-python-clis","Local State and SQLite in Python CLIs",{"path":1888,"title":1889},"\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":1891,"title":1892},"\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":1894,"title":1895},"\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":1897,"title":1898},"\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":1900,"title":1901},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fhandling-sigterm-and-graceful-shutdown","Handling SIGTERM and Graceful Shutdown in CLIs",{"path":1903,"title":1904},"\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":1906,"title":1907},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis","Long-Running and Watch-Mode Python CLIs",{"path":1909,"title":1910},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Freloading-config-on-sighup","Reloading Configuration on SIGHUP in a Python CLI",{"path":1912,"title":1913},"\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":1915,"title":1916},"\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":1918,"title":1919},"\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":1921,"title":1922},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Favoiding-shell-injection-in-python-clis","Avoiding Shell Injection in Python CLIs",{"path":1924,"title":1925},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fcalling-external-commands-safely-with-subprocess","Calling External Commands Safely with subprocess",{"path":1927,"title":1928},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fhandling-subprocess-timeouts-and-exit-codes","Handling Subprocess Timeouts and Exit Codes",{"path":1930,"title":1931},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis","Running Subprocesses from Python CLIs",{"path":1933,"title":1934},"\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":1936,"title":1937},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fpiping-between-subprocesses-in-python","Piping Between Subprocesses in Python Without a Shell",{"path":1939,"title":1940},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fstreaming-subprocess-output-in-real-time","Streaming Subprocess Output in Real Time",{"path":1942,"title":1943},"\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":1945,"title":1946},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis","Secrets and Credentials in Python CLIs",{"path":1948,"title":1949},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fprompting-for-passwords-securely","Prompting for Passwords Securely in Python CLIs",{"path":1951,"title":1952},"\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":1954,"title":1955},"\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":1957,"title":1958},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Frefreshing-expired-tokens-automatically","Refreshing Expired Tokens Automatically in a Python CLI",{"path":1960,"title":1961},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fstoring-tokens-with-keyring","Storing CLI Tokens Securely with keyring",{"path":1963,"title":1964},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fsupporting-multiple-profiles-and-accounts","Supporting Multiple Profiles and Accounts in CLIs",{"path":1966,"title":1967},"\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":1969,"title":1970},"\u002Fcli-runtime-systems-integration\u002Fupdate-checks-and-self-updating-clis","Update Checks, Upgrade Commands and Telemetry for Python CLIs",{"path":1972,"title":1973},"\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":1975,"title":1976},"\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":1978,"title":1979},"\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":1156,"title":1981},"Python CLI Toolcraft",{"path":1983,"title":1984},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cleo","Building a Python CLI with Cleo Command Classes",{"path":1986,"title":1987},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cyclopts","Building a Type-Hinted Python CLI with Cyclopts",{"path":1989,"title":1990},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks","Beyond Click and Typer: Alternative Python CLI Frameworks",{"path":1992,"title":1993},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fquick-clis-from-functions-with-python-fire","Quick CLIs from Functions with Python Fire",{"path":1995,"title":1996},"\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":1998,"title":1999},"\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":2001,"title":2002},"\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":2004,"title":2005},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fguarding-startup-with-import-tests","Guarding CLI Startup with Import Tests",{"path":2007,"title":2008},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading","CLI Startup Performance and Lazy Loading",{"path":2010,"title":2011},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Flazy-loading-subcommands-for-faster-startup","Lazy Loading Subcommands for Faster Startup",{"path":2013,"title":2014},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fprofiling-python-cli-startup-time","Profiling Python CLI Startup Time",{"path":2016,"title":2017},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Freducing-cli-dependency-weight","Reducing CLI Dependency Weight",{"path":2019,"title":2020},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-subparsers-for-subcommands","argparse Subparsers for Subcommands",{"path":2022,"title":2023},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-vs-click-vs-typer-comparison","argparse vs Click vs Typer Compared",{"path":2025,"title":2026},"\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":2028,"title":2029},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse","Command-Line Parsing with argparse",{"path":2031,"title":2032},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmigrating-from-argparse-to-typer","Migrating from argparse to Typer",{"path":2034,"title":2035},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmutually-exclusive-options-in-argparse","Mutually Exclusive Options in argparse",{"path":2037,"title":2038},"\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":2040,"title":2041},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fwriting-custom-argparse-actions","Writing Custom argparse Actions in Python",{"path":2043,"title":2044},"\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":2046,"title":2047},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fdesigning-idempotent-commands","Designing Idempotent Commands in a Python CLI",{"path":2049,"title":2050},"\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":2052,"title":2053},"\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":2055,"title":2056},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions","Designing CLI Interfaces and Conventions in Python",{"path":2058,"title":2059},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fnaming-commands-and-flags-consistently","Naming Commands and Flags Consistently in Python CLIs",{"path":2061,"title":2062},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fpositional-arguments-vs-options","Positional Arguments vs Options: Designing a CLI Signature",{"path":2064,"title":2065},"\u002Fmodern-python-cli-frameworks-architecture","Python CLI Frameworks and Architecture",{"path":2067,"title":2068},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fdiscovering-plugins-with-entry-points","Discovering Plugins with Entry Points in Python CLIs",{"path":2070,"title":2071},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fhook-based-plugins-with-pluggy","Hook-Based Plugins for Python CLIs with pluggy",{"path":2073,"title":2074},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis","Plugin Architectures for Extensible CLIs",{"path":2076,"title":2077},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fisolating-plugin-failures","Isolating Plugin Failures in an Extensible Python CLI",{"path":2079,"title":2080},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Ftesting-plugins-against-the-host-cli","Testing Plugins Against the Host CLI",{"path":2082,"title":2083},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fversioning-a-plugin-api","Versioning a Plugin API for a Python CLI",{"path":2085,"title":2086},"\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":2088,"title":2089},"\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":2091,"title":2092},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fdependency-injection-patterns-for-cli-commands","Dependency Injection Patterns for CLI Commands",{"path":2094,"title":2095},"\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":2097,"title":2098},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis","Structuring Multi-Command Python CLIs",{"path":2100,"title":2101},"\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":2103,"title":2104},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fregistering-commands-from-modules-automatically","Registering CLI Commands from Modules Automatically",{"path":2106,"title":2107},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-common-options-across-commands","Sharing Common Options Across Python CLI Commands",{"path":2109,"title":2110},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-state-with-click-context-objects","Sharing State with Click Context Objects",{"path":2112,"title":2113},"\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":2115,"title":2116},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications","Testing Python CLI Applications",{"path":2118,"title":2119},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fmeasuring-cli-test-coverage","Measuring CLI Test Coverage",{"path":2121,"title":2122},"\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":2124,"title":2125},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fproperty-based-testing-cli-arguments-with-hypothesis","Property-Based Testing CLI Arguments with Hypothesis",{"path":2127,"title":2128},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fsnapshot-testing-cli-output","Snapshot Testing CLI Output",{"path":2130,"title":2131},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-click-commands-with-clirunner","Testing Click Commands with CliRunner",{"path":2133,"title":2134},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-commands-that-call-subprocesses","Testing Python CLI Commands That Call Subprocesses",{"path":2136,"title":2137},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-interactive-prompts-and-stdin","Testing Interactive Prompts and stdin",{"path":2139,"title":2140},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftranscript-tests-for-cli-commands","Transcript Tests for Python CLI Commands",{"path":2142,"title":2143},"\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":2145,"title":2146},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fbuilding-dynamic-commands-in-click","Building Dynamic Commands in Click",{"path":2148,"title":2149},"\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":2151,"title":2152},"\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":2154,"title":2155},"\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":2157,"title":2158},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each","Typer vs Click: When to Use Each",{"path":2160,"title":2161},"\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":2163,"title":2164},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Ftyper-callback-functions-explained","Typer callback functions explained",{"path":2166,"title":2167},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fusing-annotated-options-in-typer","Using Annotated Options in Typer",{"path":2169,"title":2170},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fautomating-releases-from-git-tags","Automating Python CLI Releases from Git Tags",{"path":2172,"title":2173},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fcaching-uv-dependencies-in-ci","Caching uv Dependencies in CI for Python CLIs",{"path":2175,"title":2176},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis","CI\u002FCD Pipelines for Python CLIs",{"path":2178,"title":2179},"\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":2181,"title":2182},"\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":2184,"title":2185},"\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":2187,"title":2188},"\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":2190,"title":2191},"\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":2193,"title":2194},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fbuilding-a-cookiecutter-template-for-typer-clis","Building a Cookiecutter Template for Typer CLIs",{"path":2196,"title":2197},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fcopier-vs-cookiecutter-for-cli-templates","Copier vs Cookiecutter for CLI Templates",{"path":2199,"title":2200},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter","CLI Project Scaffolding with Cookiecutter",{"path":2202,"title":2203},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fpost-generation-hooks-in-cli-templates","Post-Generation Hooks in Python CLI Templates",{"path":2205,"title":2206},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftemplate-variables-and-conditional-files","Template Variables and Conditional Files in CLI Templates",{"path":2208,"title":2209},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftesting-a-project-template-with-pytest","Testing a CLI Project Template with pytest",{"path":1553,"title":5},{"path":2212,"title":2213},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbuilding-cross-platform-release-binaries-in-ci","Building Cross-Platform Release Binaries in CI",{"path":2215,"title":2216},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbundling-a-python-cli-with-pyinstaller","Bundling a Python CLI with PyInstaller",{"path":2218,"title":2219},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fcode-signing-and-notarizing-cli-binaries","Code Signing and Notarizing Python CLI Binaries",{"path":2221,"title":2222},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fhomebrew-and-scoop-packaging-for-python-clis","Homebrew and Scoop Packaging for Python CLIs",{"path":2224,"title":2225},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries","Distributing CLIs as Standalone Binaries",{"path":2227,"title":2228},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fnuitka-vs-pyinstaller-for-python-clis","Nuitka vs PyInstaller for Python CLI Binaries",{"path":2230,"title":2231},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Freducing-pyinstaller-binary-size","Reducing the Size of a PyInstaller CLI Binary",{"path":2233,"title":2234},"\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":2236,"title":2237},"\u002Fproject-setup-dependency-management","Project Setup & Dependency Management",{"path":2239,"title":2240},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fconfiguring-ruff-for-a-cli-project","Configuring Ruff for a Python CLI Project",{"path":2242,"title":2243},"\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":2245,"title":2246},"\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":2248,"title":2249},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code","Linting and Type-Checking Python CLI Code",{"path":2251,"title":2252},"\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":2254,"title":2255},"\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":2257,"title":2258},"\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":2260,"title":2261},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fautomating-changelogs-with-conventional-commits","Automating Changelogs with Conventional Commits",{"path":2263,"title":2264},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fbumping-versions-consistently-across-a-cli-project","Bumping Versions Consistently Across a Python CLI Project",{"path":2266,"title":2267},"\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":2269,"title":2270},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fexposing-version-info-and-build-metadata","Exposing Version Info and Build Metadata",{"path":2272,"title":2273},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs","Managing CLI Versioning & Changelogs",{"path":2275,"title":2276},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fsemantic-versioning-policy-for-cli-tools","A Semantic Versioning Policy for CLI Tools",{"path":2278,"title":2279},"\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":2281,"title":2282},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbuilding-wheels-and-sdists-for-python-clis","Building Wheels and sdists for Python CLIs",{"path":2284,"title":2285},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbundling-data-files-with-importlib-resources","Bundling Data Files with importlib.resources in CLIs",{"path":2287,"title":2288},"\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":2290,"title":2291},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution","Packaging Python CLIs for Distribution",{"path":2293,"title":2294},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Finstalling-and-distributing-clis-with-pipx","Installing and Distributing CLIs with pipx",{"path":2296,"title":2297},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Foptional-dependencies-and-extras-for-clis","Optional Dependencies and Extras for Python CLIs",{"path":2299,"title":2300},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fpublishing-a-python-cli-to-pypi","Publishing a Python CLI to PyPI",{"path":2302,"title":2303},"\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":2305,"title":2306},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fdynamic-versioning-with-poetry-plugins","Dynamic Versioning for a Poetry CLI from Git Tags",{"path":2308,"title":2309},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development","Poetry Workflows for CLI Development",{"path":2311,"title":2312},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fmanaging-poetry-lock-files-for-cli-tools","Managing Poetry Lock Files for CLI Tools",{"path":2314,"title":2315},"\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":2317,"title":2318},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-dependency-groups-for-cli-tooling","Poetry Dependency Groups for CLI Tooling",{"path":2320,"title":2321},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-entry-points-and-scripts-for-clis","Poetry Entry Points and Scripts for CLIs",{"path":2323,"title":2324},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpublishing-a-cli-with-poetry","Building and Publishing a Python CLI with Poetry",{"path":2326,"title":2327},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects","Pre-commit Hooks for CLI Projects",{"path":2329,"title":2330},"\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":2332,"title":2333},"\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":2335,"title":1518},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects\u002Fsetting-up-pre-commit-for-python-cli-repos",{"path":2337,"title":2338},"\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":2340,"title":2341},"\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":2343,"title":2344},"\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":2346,"title":2347},"\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":2349,"title":2350},"\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":2352,"title":2353},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain","Securing the Supply Chain of a Python CLI",{"path":2355,"title":2356},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpinning-dependencies-with-hashes","Pinning a Python CLI’s Dependencies with Hashes",{"path":2358,"title":2359},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpublishing-attestations-and-verifying-releases","Publishing Attestations and Verifying Python CLI Releases",{"path":2361,"title":2362},"\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":2364,"title":2365},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management","uv for Python CLI Dependency Management",{"path":2367,"title":2368},"\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":2370,"title":2371},"\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":2373,"title":2374},"\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":2376,"title":2377},"\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":2379,"title":2380},"\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":2382,"title":2383},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis","uv Workspaces for Multi-Package Python CLIs",{"path":2385,"title":2386},"\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":2388,"title":2389},"\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":2391,"title":2392},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices","Python CLI Env Isolation Best Practices",{"path":2394,"title":2395},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fisolating-cli-tools-from-project-dependencies","Isolating CLI Tools from Your Project’s Dependencies",{"path":2397,"title":2398},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fmanaging-virtual-environments-for-cross-platform-clis","Managing Python CLI Virtual Environments",{"path":2400,"title":2401},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fpinning-the-python-version-for-a-cli","Pinning the Python Version for a CLI",{"path":2403,"title":2404},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fsupporting-multiple-python-versions-with-nox","Supporting Multiple Python Versions with nox",1790967542190]