[{"data":1,"prerenderedAt":2285},["ShallowReactive",2],{"page-\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fpublishing-a-cli-docker-image-from-ci\u002F":3,"content-directory":1440},{"id":4,"title":5,"body":6,"date":1425,"description":1426,"difficulty":1427,"draft":1428,"extension":1429,"meta":1430,"navigation":122,"path":1431,"seo":1432,"stem":1433,"tags":1434,"updated":1425,"__hash__":1439},"content\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fpublishing-a-cli-docker-image-from-ci\u002Findex.md","Publishing a Python CLI as a Docker Image from CI",{"type":7,"value":8,"toc":1408},"minimark",[9,24,29,54,58,208,216,220,251,255,698,752,755,762,766,769,866,903,906,909,913,986,990,993,1289,1304,1308,1318,1322,1327,1334,1338,1341,1345,1348,1352,1355,1359,1369,1373,1404],[10,11,12,13,17,18,23],"p",{},"Some users never want to install Python at all. A CI pipeline that runs your linter, a platform team standardising tools across languages, a Kubernetes job that runs a data export every night — for all of them, ",[14,15,16],"code",{},"docker run ghcr.io\u002Facme\u002Fmytool:1.6 …"," is the natural way to consume a CLI. A container image also gives you something no wheel can: a fully pinned, reproducible environment including the interpreter, built once and run identically everywhere. Publishing one well takes a little care — a small image, a non-root user, sensible tags, multi-architecture builds for Apple silicon and ARM servers, provenance attached — and some thought about how a CLI behaves inside a container, where the user's files, terminal and identity are all on the other side of a boundary. This guide covers both. It belongs to the ",[19,20,22],"a",{"href":21},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002F","CI\u002FCD topic",".",[25,26,28],"h2",{"id":27},"prerequisites","Prerequisites",[30,31,32,44,51],"ul",{},[33,34,35,36,39,40,23],"li",{},"A CLI that builds as a wheel, with a ",[14,37,38],{},"uv.lock","; see ",[19,41,43],{"href":42},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fbuilding-and-publishing-a-cli-with-uv\u002F","building and publishing a CLI with uv",[33,45,46,47,50],{},"A GitHub repository (the examples publish to GitHub Container Registry, ",[14,48,49],{},"ghcr.io",").",[33,52,53],{},"Docker with Buildx locally, for testing the image before CI does.",[25,55,57],{"id":56},"the-image","The image",[59,60,65],"pre",{"className":61,"code":62,"language":63,"meta":64,"style":64},"language-dockerfile shiki shiki-themes github-light github-dark","# Dockerfile\nFROM python:3.13-slim AS build\nCOPY --from=ghcr.io\u002Fastral-sh\u002Fuv:0.8 \u002Fuv \u002Fbin\u002Fuv\nWORKDIR \u002Fsrc\nCOPY pyproject.toml uv.lock .\u002F\nRUN uv export --frozen --no-dev --no-emit-project --format requirements.txt -o \u002Frequirements.txt\nCOPY . .\nRUN uv build --wheel --out-dir \u002Fdist\n\nFROM python:3.13-slim\nARG VERSION=dev\nLABEL org.opencontainers.image.title=\"mytool\" \\\n      org.opencontainers.image.version=\"${VERSION}\" \\\n      org.opencontainers.image.source=\"https:\u002F\u002Fgithub.com\u002Facme\u002Fmytool\"\nENV PYTHONDONTWRITEBYTECODE=1 PYTHONUNBUFFERED=1 PYTHONUTF8=1\nCOPY --from=build \u002Frequirements.txt \u002Fdist\u002F \u002Ftmp\u002Finstall\u002F\nRUN python -m pip install --no-cache-dir --require-hashes --no-deps -r \u002Ftmp\u002Finstall\u002Frequirements.txt \\\n && python -m pip install --no-cache-dir --no-deps \u002Ftmp\u002Finstall\u002F*.whl \\\n && rm -rf \u002Ftmp\u002Finstall\nUSER 65532:65532\nWORKDIR \u002Fwork\nENTRYPOINT [\"mytool\"]\nCMD [\"--help\"]\n","dockerfile","",[14,66,67,75,81,87,93,99,105,111,117,124,130,136,142,148,154,160,166,172,178,184,190,196,202],{"__ignoreMap":64},[68,69,72],"span",{"class":70,"line":71},"line",1,[68,73,74],{},"# Dockerfile\n",[68,76,78],{"class":70,"line":77},2,[68,79,80],{},"FROM python:3.13-slim AS build\n",[68,82,84],{"class":70,"line":83},3,[68,85,86],{},"COPY --from=ghcr.io\u002Fastral-sh\u002Fuv:0.8 \u002Fuv \u002Fbin\u002Fuv\n",[68,88,90],{"class":70,"line":89},4,[68,91,92],{},"WORKDIR \u002Fsrc\n",[68,94,96],{"class":70,"line":95},5,[68,97,98],{},"COPY pyproject.toml uv.lock .\u002F\n",[68,100,102],{"class":70,"line":101},6,[68,103,104],{},"RUN uv export --frozen --no-dev --no-emit-project --format requirements.txt -o \u002Frequirements.txt\n",[68,106,108],{"class":70,"line":107},7,[68,109,110],{},"COPY . .\n",[68,112,114],{"class":70,"line":113},8,[68,115,116],{},"RUN uv build --wheel --out-dir \u002Fdist\n",[68,118,120],{"class":70,"line":119},9,[68,121,123],{"emptyLinePlaceholder":122},true,"\n",[68,125,127],{"class":70,"line":126},10,[68,128,129],{},"FROM python:3.13-slim\n",[68,131,133],{"class":70,"line":132},11,[68,134,135],{},"ARG VERSION=dev\n",[68,137,139],{"class":70,"line":138},12,[68,140,141],{},"LABEL org.opencontainers.image.title=\"mytool\" \\\n",[68,143,145],{"class":70,"line":144},13,[68,146,147],{},"      org.opencontainers.image.version=\"${VERSION}\" \\\n",[68,149,151],{"class":70,"line":150},14,[68,152,153],{},"      org.opencontainers.image.source=\"https:\u002F\u002Fgithub.com\u002Facme\u002Fmytool\"\n",[68,155,157],{"class":70,"line":156},15,[68,158,159],{},"ENV PYTHONDONTWRITEBYTECODE=1 PYTHONUNBUFFERED=1 PYTHONUTF8=1\n",[68,161,163],{"class":70,"line":162},16,[68,164,165],{},"COPY --from=build \u002Frequirements.txt \u002Fdist\u002F \u002Ftmp\u002Finstall\u002F\n",[68,167,169],{"class":70,"line":168},17,[68,170,171],{},"RUN python -m pip install --no-cache-dir --require-hashes --no-deps -r \u002Ftmp\u002Finstall\u002Frequirements.txt \\\n",[68,173,175],{"class":70,"line":174},18,[68,176,177],{}," && python -m pip install --no-cache-dir --no-deps \u002Ftmp\u002Finstall\u002F*.whl \\\n",[68,179,181],{"class":70,"line":180},19,[68,182,183],{}," && rm -rf \u002Ftmp\u002Finstall\n",[68,185,187],{"class":70,"line":186},20,[68,188,189],{},"USER 65532:65532\n",[68,191,193],{"class":70,"line":192},21,[68,194,195],{},"WORKDIR \u002Fwork\n",[68,197,199],{"class":70,"line":198},22,[68,200,201],{},"ENTRYPOINT [\"mytool\"]\n",[68,203,205],{"class":70,"line":204},23,[68,206,207],{},"CMD [\"--help\"]\n",[10,209,210,211,215],{},"The build stage exports a hashed requirements file from the lock and builds the wheel; the final stage contains only Python, your dependencies — installed with their hashes enforced, as described in ",[19,212,214],{"href":213},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpinning-dependencies-with-hashes\u002F","pinning dependencies with hashes"," — and your package. uv and the source tree stay behind in the build stage.",[217,218],"inline-diagram",{"name":219},"docker-image-layers",[10,221,222,223,226,227,230,231,234,235,238,239,242,243,246,247,250],{},"A few lines deserve explanation. ",[14,224,225],{},"ENTRYPOINT [\"mytool\"]"," makes the image behave like the command: ",[14,228,229],{},"docker run image status"," runs ",[14,232,233],{},"mytool status",". ",[14,236,237],{},"CMD [\"--help\"]"," is the default argument list, so running the image with no arguments prints help instead of doing nothing. ",[14,240,241],{},"USER 65532:65532"," runs as an unprivileged user — a compromised dependency inside the container then cannot modify the image's files. ",[14,244,245],{},"WORKDIR \u002Fwork"," gives users a conventional mount point. ",[14,248,249],{},"PYTHONUNBUFFERED=1"," makes output appear immediately in CI logs instead of in bursts.",[25,252,254],{"id":253},"publishing-from-ci","Publishing from CI",[59,256,260],{"className":257,"code":258,"language":259,"meta":64,"style":64},"language-yaml shiki shiki-themes github-light github-dark","# .github\u002Fworkflows\u002Fimage.yml\nname: image\non:\n  push:\n    tags: [\"v*\"]\n    branches: [main]\n\npermissions:\n  contents: read\n  packages: write\n  id-token: write\n  attestations: write\n\njobs:\n  image:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: docker\u002Fsetup-qemu-action@v3\n      - uses: docker\u002Fsetup-buildx-action@v3\n      - uses: docker\u002Flogin-action@v3\n        with:\n          registry: ghcr.io\n          username: ${{ github.actor }}\n          password: ${{ secrets.GITHUB_TOKEN }}\n      - id: meta\n        uses: docker\u002Fmetadata-action@v5\n        with:\n          images: ghcr.io\u002F${{ github.repository }}\n          tags: |\n            type=semver,pattern={{version}}\n            type=semver,pattern={{major}}.{{minor}}\n            type=semver,pattern={{major}}\n            type=edge,branch=main\n      - uses: docker\u002Fbuild-push-action@v6\n        with:\n          context: .\n          platforms: linux\u002Famd64,linux\u002Farm64\n          push: true\n          tags: ${{ steps.meta.outputs.tags }}\n          labels: ${{ steps.meta.outputs.labels }}\n          build-args: VERSION=${{ steps.meta.outputs.version }}\n          provenance: mode=max\n          sbom: true\n          cache-from: type=gha\n          cache-to: type=gha,mode=max\n","yaml",[14,261,262,268,282,291,298,312,324,328,335,345,355,364,373,377,384,391,401,408,421,432,443,454,461,471,482,493,506,517,524,535,547,553,559,565,571,583,590,601,612,623,633,644,655,666,676,687],{"__ignoreMap":64},[68,263,264],{"class":70,"line":71},[68,265,267],{"class":266},"sJ8bj","# .github\u002Fworkflows\u002Fimage.yml\n",[68,269,270,274,278],{"class":70,"line":77},[68,271,273],{"class":272},"s9eBZ","name",[68,275,277],{"class":276},"sVt8B",": ",[68,279,281],{"class":280},"sZZnC","image\n",[68,283,284,288],{"class":70,"line":83},[68,285,287],{"class":286},"sj4cs","on",[68,289,290],{"class":276},":\n",[68,292,293,296],{"class":70,"line":89},[68,294,295],{"class":272},"  push",[68,297,290],{"class":276},[68,299,300,303,306,309],{"class":70,"line":95},[68,301,302],{"class":272},"    tags",[68,304,305],{"class":276},": [",[68,307,308],{"class":280},"\"v*\"",[68,310,311],{"class":276},"]\n",[68,313,314,317,319,322],{"class":70,"line":101},[68,315,316],{"class":272},"    branches",[68,318,305],{"class":276},[68,320,321],{"class":280},"main",[68,323,311],{"class":276},[68,325,326],{"class":70,"line":107},[68,327,123],{"emptyLinePlaceholder":122},[68,329,330,333],{"class":70,"line":113},[68,331,332],{"class":272},"permissions",[68,334,290],{"class":276},[68,336,337,340,342],{"class":70,"line":119},[68,338,339],{"class":272},"  contents",[68,341,277],{"class":276},[68,343,344],{"class":280},"read\n",[68,346,347,350,352],{"class":70,"line":126},[68,348,349],{"class":272},"  packages",[68,351,277],{"class":276},[68,353,354],{"class":280},"write\n",[68,356,357,360,362],{"class":70,"line":132},[68,358,359],{"class":272},"  id-token",[68,361,277],{"class":276},[68,363,354],{"class":280},[68,365,366,369,371],{"class":70,"line":138},[68,367,368],{"class":272},"  attestations",[68,370,277],{"class":276},[68,372,354],{"class":280},[68,374,375],{"class":70,"line":144},[68,376,123],{"emptyLinePlaceholder":122},[68,378,379,382],{"class":70,"line":150},[68,380,381],{"class":272},"jobs",[68,383,290],{"class":276},[68,385,386,389],{"class":70,"line":156},[68,387,388],{"class":272},"  image",[68,390,290],{"class":276},[68,392,393,396,398],{"class":70,"line":162},[68,394,395],{"class":272},"    runs-on",[68,397,277],{"class":276},[68,399,400],{"class":280},"ubuntu-latest\n",[68,402,403,406],{"class":70,"line":168},[68,404,405],{"class":272},"    steps",[68,407,290],{"class":276},[68,409,410,413,416,418],{"class":70,"line":174},[68,411,412],{"class":276},"      - ",[68,414,415],{"class":272},"uses",[68,417,277],{"class":276},[68,419,420],{"class":280},"actions\u002Fcheckout@v4\n",[68,422,423,425,427,429],{"class":70,"line":180},[68,424,412],{"class":276},[68,426,415],{"class":272},[68,428,277],{"class":276},[68,430,431],{"class":280},"docker\u002Fsetup-qemu-action@v3\n",[68,433,434,436,438,440],{"class":70,"line":186},[68,435,412],{"class":276},[68,437,415],{"class":272},[68,439,277],{"class":276},[68,441,442],{"class":280},"docker\u002Fsetup-buildx-action@v3\n",[68,444,445,447,449,451],{"class":70,"line":192},[68,446,412],{"class":276},[68,448,415],{"class":272},[68,450,277],{"class":276},[68,452,453],{"class":280},"docker\u002Flogin-action@v3\n",[68,455,456,459],{"class":70,"line":198},[68,457,458],{"class":272},"        with",[68,460,290],{"class":276},[68,462,463,466,468],{"class":70,"line":204},[68,464,465],{"class":272},"          registry",[68,467,277],{"class":276},[68,469,470],{"class":280},"ghcr.io\n",[68,472,474,477,479],{"class":70,"line":473},24,[68,475,476],{"class":272},"          username",[68,478,277],{"class":276},[68,480,481],{"class":280},"${{ github.actor }}\n",[68,483,485,488,490],{"class":70,"line":484},25,[68,486,487],{"class":272},"          password",[68,489,277],{"class":276},[68,491,492],{"class":280},"${{ secrets.GITHUB_TOKEN }}\n",[68,494,496,498,501,503],{"class":70,"line":495},26,[68,497,412],{"class":276},[68,499,500],{"class":272},"id",[68,502,277],{"class":276},[68,504,505],{"class":280},"meta\n",[68,507,509,512,514],{"class":70,"line":508},27,[68,510,511],{"class":272},"        uses",[68,513,277],{"class":276},[68,515,516],{"class":280},"docker\u002Fmetadata-action@v5\n",[68,518,520,522],{"class":70,"line":519},28,[68,521,458],{"class":272},[68,523,290],{"class":276},[68,525,527,530,532],{"class":70,"line":526},29,[68,528,529],{"class":272},"          images",[68,531,277],{"class":276},[68,533,534],{"class":280},"ghcr.io\u002F${{ github.repository }}\n",[68,536,538,541,543],{"class":70,"line":537},30,[68,539,540],{"class":272},"          tags",[68,542,277],{"class":276},[68,544,546],{"class":545},"szBVR","|\n",[68,548,550],{"class":70,"line":549},31,[68,551,552],{"class":280},"            type=semver,pattern={{version}}\n",[68,554,556],{"class":70,"line":555},32,[68,557,558],{"class":280},"            type=semver,pattern={{major}}.{{minor}}\n",[68,560,562],{"class":70,"line":561},33,[68,563,564],{"class":280},"            type=semver,pattern={{major}}\n",[68,566,568],{"class":70,"line":567},34,[68,569,570],{"class":280},"            type=edge,branch=main\n",[68,572,574,576,578,580],{"class":70,"line":573},35,[68,575,412],{"class":276},[68,577,415],{"class":272},[68,579,277],{"class":276},[68,581,582],{"class":280},"docker\u002Fbuild-push-action@v6\n",[68,584,586,588],{"class":70,"line":585},36,[68,587,458],{"class":272},[68,589,290],{"class":276},[68,591,593,596,598],{"class":70,"line":592},37,[68,594,595],{"class":272},"          context",[68,597,277],{"class":276},[68,599,600],{"class":286},".\n",[68,602,604,607,609],{"class":70,"line":603},38,[68,605,606],{"class":272},"          platforms",[68,608,277],{"class":276},[68,610,611],{"class":280},"linux\u002Famd64,linux\u002Farm64\n",[68,613,615,618,620],{"class":70,"line":614},39,[68,616,617],{"class":272},"          push",[68,619,277],{"class":276},[68,621,622],{"class":286},"true\n",[68,624,626,628,630],{"class":70,"line":625},40,[68,627,540],{"class":272},[68,629,277],{"class":276},[68,631,632],{"class":280},"${{ steps.meta.outputs.tags }}\n",[68,634,636,639,641],{"class":70,"line":635},41,[68,637,638],{"class":272},"          labels",[68,640,277],{"class":276},[68,642,643],{"class":280},"${{ steps.meta.outputs.labels }}\n",[68,645,647,650,652],{"class":70,"line":646},42,[68,648,649],{"class":272},"          build-args",[68,651,277],{"class":276},[68,653,654],{"class":280},"VERSION=${{ steps.meta.outputs.version }}\n",[68,656,658,661,663],{"class":70,"line":657},43,[68,659,660],{"class":272},"          provenance",[68,662,277],{"class":276},[68,664,665],{"class":280},"mode=max\n",[68,667,669,672,674],{"class":70,"line":668},44,[68,670,671],{"class":272},"          sbom",[68,673,277],{"class":276},[68,675,622],{"class":286},[68,677,679,682,684],{"class":70,"line":678},45,[68,680,681],{"class":272},"          cache-from",[68,683,277],{"class":276},[68,685,686],{"class":280},"type=gha\n",[68,688,690,693,695],{"class":70,"line":689},46,[68,691,692],{"class":272},"          cache-to",[68,694,277],{"class":276},[68,696,697],{"class":280},"type=gha,mode=max\n",[10,699,700,701,704,705,708,709,712,713,716,717,719,720,723,724,726,727,729,730,732,733,712,736,739,740,712,743,746,747,751],{},"The metadata action turns a ",[14,702,703],{},"v1.6.2"," tag into the image tags ",[14,706,707],{},"1.6.2",", ",[14,710,711],{},"1.6"," and ",[14,714,715],{},"1",", and pushes to ",[14,718,321],{}," into an ",[14,721,722],{},"edge"," tag. Users choose their stability: pin ",[14,725,707],{}," for reproducibility, follow ",[14,728,711],{}," for patch releases, or track ",[14,731,715],{},". QEMU plus Buildx produce ",[14,734,735],{},"linux\u002Famd64",[14,737,738],{},"linux\u002Farm64"," variants under one tag, so the image runs natively on Apple silicon laptops and ARM servers. ",[14,741,742],{},"provenance: mode=max",[14,744,745],{},"sbom: true"," attach a build provenance attestation and a software bill of materials to the image — the container counterpart of ",[19,748,750],{"href":749},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fgenerating-an-sbom-for-a-python-cli\u002F","generating an SBOM for a Python CLI",". The GitHub Actions cache keeps rebuilds fast. Pin each action to a commit SHA in a real workflow.",[217,753],{"name":754},"docker-tags",[10,756,757,758,761],{},"A plain ",[14,759,760],{},"latest"," tag is deliberately absent. \"Latest\" is ambiguous — latest release, or latest build of main? — and it silently changes under scripts. The semver tags say what they mean.",[25,763,765],{"id":764},"running-a-cli-in-a-container","Running a CLI in a container",[10,767,768],{},"A CLI in a container sees its own filesystem, its own user and, by default, no terminal. Document the invocation that makes it feel native:",[59,770,774],{"className":771,"code":772,"language":773,"meta":64,"style":64},"language-bash shiki shiki-themes github-light github-dark","docker run --rm -it \\\n  --user \"$(id -u):$(id -g)\" \\\n  -v \"$PWD:\u002Fwork\" -w \u002Fwork \\\n  -e MYTOOL_TOKEN \\\n  ghcr.io\u002Facme\u002Fmytool:1.6 export --to report.csv\n","bash",[14,775,776,794,820,842,852],{"__ignoreMap":64},[68,777,778,782,785,788,791],{"class":70,"line":71},[68,779,781],{"class":780},"sScJk","docker",[68,783,784],{"class":280}," run",[68,786,787],{"class":286}," --rm",[68,789,790],{"class":286}," -it",[68,792,793],{"class":286}," \\\n",[68,795,796,799,802,804,807,810,812,815,818],{"class":70,"line":77},[68,797,798],{"class":286},"  --user",[68,800,801],{"class":280}," \"$(",[68,803,500],{"class":780},[68,805,806],{"class":286}," -u",[68,808,809],{"class":280},"):$(",[68,811,500],{"class":780},[68,813,814],{"class":286}," -g",[68,816,817],{"class":280},")\"",[68,819,793],{"class":286},[68,821,822,825,828,831,834,837,840],{"class":70,"line":83},[68,823,824],{"class":286},"  -v",[68,826,827],{"class":280}," \"",[68,829,830],{"class":276},"$PWD",[68,832,833],{"class":280},":\u002Fwork\"",[68,835,836],{"class":286}," -w",[68,838,839],{"class":280}," \u002Fwork",[68,841,793],{"class":286},[68,843,844,847,850],{"class":70,"line":89},[68,845,846],{"class":286},"  -e",[68,848,849],{"class":280}," MYTOOL_TOKEN",[68,851,793],{"class":286},[68,853,854,857,860,863],{"class":70,"line":95},[68,855,856],{"class":280},"  ghcr.io\u002Facme\u002Fmytool:1.6",[68,858,859],{"class":280}," export",[68,861,862],{"class":286}," --to",[68,864,865],{"class":280}," report.csv\n",[30,867,868,874,885,891,897],{},[33,869,870,873],{},[14,871,872],{},"--rm"," removes the container afterwards; nobody wants hundreds of stopped containers.",[33,875,876,879,880,884],{},[14,877,878],{},"-it"," attaches a terminal, so colours, prompts and progress bars work. Drop it in CI, where there is no TTY — the CLI's own ",[19,881,883],{"href":882},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fdetecting-tty-and-adapting-output\u002F","TTY detection"," then switches to plain output.",[33,886,887,890],{},[14,888,889],{},"--user \"$(id -u):$(id -g)\""," makes files written to the mounted directory belong to the user, not to UID 65532.",[33,892,893,896],{},[14,894,895],{},"-v \"$PWD:\u002Fwork\" -w \u002Fwork"," makes relative paths behave as on the host.",[33,898,899,902],{},[14,900,901],{},"-e MYTOOL_TOKEN"," passes a secret from the host environment by name, without writing it on the command line.",[10,904,905],{},"Many users wrap that in a shell alias or function — publish one in the README.",[217,907],{"name":908},"docker-run-terminal",[25,910,912],{"id":911},"ux-considerations","UX considerations",[30,914,915,926,936,962,980],{},[33,916,917,921,922,925],{},[918,919,920],"strong",{},"Keep stdout clean."," In containers, logs and data share the same streams as on the host. Diagnostics on stderr, data on stdout — as everywhere — so ",[14,923,924],{},"docker run … > out.json"," works.",[33,927,928,931,932,23],{},[918,929,930],{},"Never bake secrets into the image."," Configuration and tokens come from environment variables or mounted files at run time; see ",[19,933,935],{"href":934},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Freading-secrets-from-env-and-files\u002F","reading secrets from env and files",[33,937,938,941,942,945,946,949,950,953,954,957,958,23],{},[918,939,940],{},"Handle signals."," ",[14,943,944],{},"docker stop"," sends SIGTERM to the entrypoint process. Because ",[14,947,948],{},"mytool"," is PID 1 in the container, default signal handling differs; add ",[14,951,952],{},"--init"," to ",[14,955,956],{},"docker run",", or handle SIGTERM explicitly as in ",[19,959,961],{"href":960},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fhandling-sigterm-and-graceful-shutdown\u002F","handling SIGTERM and graceful shutdown",[33,963,964,967,968,971,972,975,976,23],{},[918,965,966],{},"Disable update notices."," A container is immutable; telling its user to ",[14,969,970],{},"pipx upgrade"," is wrong. Set ",[14,973,974],{},"ENV MYTOOL_NO_UPDATE_CHECK=1"," in the image, as covered in ",[19,977,979],{"href":978},"\u002Fcli-runtime-systems-integration\u002Fupdate-checks-and-self-updating-clis\u002Fshowing-non-blocking-update-notices\u002F","showing non-blocking update notices",[33,981,982,985],{},[918,983,984],{},"Pin the base image by digest"," for releases, and rebuild regularly so OS security fixes reach users.",[25,987,989],{"id":988},"testing-the-behaviour","Testing the behaviour",[10,991,992],{},"Test the image itself before pushing, in the same workflow: build for the runner's architecture, load it, and run a few commands that exercise the entrypoint, the non-root user and mounted files:",[59,994,996],{"className":771,"code":995,"language":773,"meta":64,"style":64},"#!\u002Fusr\u002Fbin\u002Fenv bash\n# scripts\u002Ftest-image.sh IMAGE\nset -euo pipefail\nimage=${1:?usage: test-image.sh IMAGE}\n\ndocker run --rm \"$image\" --version\ndocker run --rm \"$image\" | grep -q \"Usage\"                       # CMD defaults to --help\ntest \"$(docker run --rm --entrypoint id \"$image\" -u)\" != \"0\"     # not running as root\n\nworkdir=$(mktemp -d)\necho '{\"name\": \"web-1\"}' > \"$workdir\u002Fin.json\"\ndocker run --rm --user \"$(id -u):$(id -g)\" -v \"$workdir:\u002Fwork\" \"$image\" \\\n    convert in.json --to out.csv\ntest -s \"$workdir\u002Fout.csv\"\ntest \"$(stat -c %u \"$workdir\u002Fout.csv\")\" = \"$(id -u)\"              # files owned by the caller\necho \"image OK\"\n",[14,997,998,1003,1008,1019,1046,1050,1069,1098,1137,1141,1160,1179,1221,1234,1248,1282],{"__ignoreMap":64},[68,999,1000],{"class":70,"line":71},[68,1001,1002],{"class":266},"#!\u002Fusr\u002Fbin\u002Fenv bash\n",[68,1004,1005],{"class":70,"line":77},[68,1006,1007],{"class":266},"# scripts\u002Ftest-image.sh IMAGE\n",[68,1009,1010,1013,1016],{"class":70,"line":83},[68,1011,1012],{"class":286},"set",[68,1014,1015],{"class":286}," -euo",[68,1017,1018],{"class":280}," pipefail\n",[68,1020,1021,1024,1027,1031,1034,1037,1040,1043],{"class":70,"line":89},[68,1022,1023],{"class":276},"image",[68,1025,1026],{"class":545},"=",[68,1028,1030],{"class":1029},"s4XuR","${1",[68,1032,1033],{"class":545},":?",[68,1035,1036],{"class":276},"usage",[68,1038,1039],{"class":545},":",[68,1041,1042],{"class":276}," test-image.sh IMAGE",[68,1044,1045],{"class":1029},"}\n",[68,1047,1048],{"class":70,"line":95},[68,1049,123],{"emptyLinePlaceholder":122},[68,1051,1052,1054,1056,1058,1060,1063,1066],{"class":70,"line":101},[68,1053,781],{"class":780},[68,1055,784],{"class":280},[68,1057,787],{"class":286},[68,1059,827],{"class":280},[68,1061,1062],{"class":276},"$image",[68,1064,1065],{"class":280},"\"",[68,1067,1068],{"class":286}," --version\n",[68,1070,1071,1073,1075,1077,1079,1081,1083,1086,1089,1092,1095],{"class":70,"line":107},[68,1072,781],{"class":780},[68,1074,784],{"class":280},[68,1076,787],{"class":286},[68,1078,827],{"class":280},[68,1080,1062],{"class":276},[68,1082,1065],{"class":280},[68,1084,1085],{"class":545}," |",[68,1087,1088],{"class":780}," grep",[68,1090,1091],{"class":286}," -q",[68,1093,1094],{"class":280}," \"Usage\"",[68,1096,1097],{"class":266},"                       # CMD defaults to --help\n",[68,1099,1100,1103,1105,1107,1110,1112,1115,1118,1120,1123,1126,1128,1131,1134],{"class":70,"line":113},[68,1101,1102],{"class":286},"test",[68,1104,801],{"class":280},[68,1106,781],{"class":780},[68,1108,1109],{"class":280}," run ",[68,1111,872],{"class":286},[68,1113,1114],{"class":286}," --entrypoint",[68,1116,1117],{"class":280}," id \"",[68,1119,1062],{"class":276},[68,1121,1122],{"class":280},"\" ",[68,1124,1125],{"class":286},"-u",[68,1127,817],{"class":280},[68,1129,1130],{"class":280}," !=",[68,1132,1133],{"class":280}," \"0\"",[68,1135,1136],{"class":266},"     # not running as root\n",[68,1138,1139],{"class":70,"line":119},[68,1140,123],{"emptyLinePlaceholder":122},[68,1142,1143,1146,1148,1151,1154,1157],{"class":70,"line":126},[68,1144,1145],{"class":276},"workdir",[68,1147,1026],{"class":545},[68,1149,1150],{"class":276},"$(",[68,1152,1153],{"class":780},"mktemp",[68,1155,1156],{"class":286}," -d",[68,1158,1159],{"class":276},")\n",[68,1161,1162,1165,1168,1171,1173,1176],{"class":70,"line":132},[68,1163,1164],{"class":286},"echo",[68,1166,1167],{"class":280}," '{\"name\": \"web-1\"}'",[68,1169,1170],{"class":545}," >",[68,1172,827],{"class":280},[68,1174,1175],{"class":276},"$workdir",[68,1177,1178],{"class":280},"\u002Fin.json\"\n",[68,1180,1181,1183,1185,1187,1190,1192,1194,1196,1198,1200,1202,1204,1207,1209,1211,1213,1215,1217,1219],{"class":70,"line":138},[68,1182,781],{"class":780},[68,1184,784],{"class":280},[68,1186,787],{"class":286},[68,1188,1189],{"class":286}," --user",[68,1191,801],{"class":280},[68,1193,500],{"class":780},[68,1195,806],{"class":286},[68,1197,809],{"class":280},[68,1199,500],{"class":780},[68,1201,814],{"class":286},[68,1203,817],{"class":280},[68,1205,1206],{"class":286}," -v",[68,1208,827],{"class":280},[68,1210,1175],{"class":276},[68,1212,833],{"class":280},[68,1214,827],{"class":280},[68,1216,1062],{"class":276},[68,1218,1065],{"class":280},[68,1220,793],{"class":286},[68,1222,1223,1226,1229,1231],{"class":70,"line":144},[68,1224,1225],{"class":280},"    convert",[68,1227,1228],{"class":280}," in.json",[68,1230,862],{"class":286},[68,1232,1233],{"class":280}," out.csv\n",[68,1235,1236,1238,1241,1243,1245],{"class":70,"line":150},[68,1237,1102],{"class":286},[68,1239,1240],{"class":286}," -s",[68,1242,827],{"class":280},[68,1244,1175],{"class":276},[68,1246,1247],{"class":280},"\u002Fout.csv\"\n",[68,1249,1250,1252,1254,1257,1260,1263,1265,1268,1271,1273,1275,1277,1279],{"class":70,"line":156},[68,1251,1102],{"class":286},[68,1253,801],{"class":280},[68,1255,1256],{"class":286},"stat",[68,1258,1259],{"class":286}," -c",[68,1261,1262],{"class":280}," %u \"",[68,1264,1175],{"class":276},[68,1266,1267],{"class":280},"\u002Fout.csv\")\"",[68,1269,1270],{"class":280}," =",[68,1272,801],{"class":280},[68,1274,500],{"class":780},[68,1276,806],{"class":286},[68,1278,817],{"class":280},[68,1280,1281],{"class":266},"              # files owned by the caller\n",[68,1283,1284,1286],{"class":70,"line":162},[68,1285,1164],{"class":286},[68,1287,1288],{"class":280}," \"image OK\"\n",[10,1290,1291,1292,1295,1296,1299,1300,1303],{},"Run it with ",[14,1293,1294],{},"docker buildx build --load -t mytool:test ."," followed by ",[14,1297,1298],{},"scripts\u002Ftest-image.sh mytool:test"," before the multi-arch push step. Container scanners (",[14,1301,1302],{},"docker scout",", Trivy, Grype) can also run here to flag vulnerable OS packages in the base image.",[25,1305,1307],{"id":1306},"conclusion","Conclusion",[10,1309,1310,1311,1314,1315,1317],{},"A container image is the most reproducible way to ship a Python CLI and the most convenient for CI-heavy users. Build it in two stages with hash-locked dependencies, run as a non-root user with ",[14,1312,1313],{},"ENTRYPOINT"," set to the command, publish multi-arch images with semver tags, provenance and an SBOM from a tag-triggered workflow, and document the ",[14,1316,956],{}," flags that make files, terminals and secrets behave. Test the image like any other artefact before it is pushed.",[25,1319,1321],{"id":1320},"frequently-asked-questions","Frequently asked questions",[1323,1324,1326],"h3",{"id":1325},"should-i-use-alpine-for-a-smaller-image","Should I use Alpine for a smaller image?",[10,1328,1329,1330,1333],{},"Usually not for Python. Alpine uses musl instead of glibc, so many binary wheels do not apply and packages build from source, making builds slower and sometimes failing. ",[14,1331,1332],{},"python:3.x-slim"," or a distroless Python image is a better size–compatibility trade-off.",[1323,1335,1337],{"id":1336},"can-the-image-be-built-without-docker-in-ci","Can the image be built without Docker in CI?",[10,1339,1340],{},"Yes — Buildah, Kaniko and similar tools build OCI images without a Docker daemon, and registries accept their output. The Dockerfile above works unchanged.",[1323,1342,1344],{"id":1343},"how-do-users-get-shell-completion-for-a-containerised-cli","How do users get shell completion for a containerised CLI?",[10,1346,1347],{},"They do not, in any convenient way: completion runs on the host shell, which cannot see inside the image. Container users are usually scripts and CI, where completion does not matter. Point interactive users at the pipx or uv install instead.",[1323,1349,1351],{"id":1350},"is-a-pyinstaller-binary-or-a-container-image-better","Is a PyInstaller binary or a container image better?",[10,1353,1354],{},"They serve different people. Binaries suit developers on laptops who want a single file; images suit CI systems, servers and organisations that standardise on containers. Many projects publish both from the same release workflow, alongside the PyPI package.",[1323,1356,1358],{"id":1357},"how-big-will-the-image-be","How big will the image be?",[10,1360,1361,1362,1364,1365,1368],{},"A ",[14,1363,1332],{}," base is a little over 100 MB uncompressed; a typical CLI and its dependencies add 10–50 MB on top. Registries and Docker transfer compressed layers, and the base layers are shared with every other image built on the same base, so the download for users who already have it is mostly your own layer. Keep that layer small by installing with ",[14,1366,1367],{},"--no-cache-dir",", leaving build tools in the build stage and not copying the source tree into the final image.",[25,1370,1372],{"id":1371},"related","Related",[30,1374,1375,1381,1387,1392,1398],{},[33,1376,1377,1378],{},"Up: ",[19,1379,1380],{"href":21},"CI\u002FCD pipelines for Python CLIs",[33,1382,1383],{},[19,1384,1386],{"href":1385},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fautomating-releases-from-git-tags\u002F","Automating releases from git tags",[33,1388,1389],{},[19,1390,1391],{"href":213},"Pinning dependencies with hashes",[33,1393,1394],{},[19,1395,1397],{"href":1396},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbuilding-cross-platform-release-binaries-in-ci\u002F","Building cross-platform release binaries in CI",[33,1399,1400],{},[19,1401,1403],{"href":1402},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Frunning-a-cli-on-a-schedule-with-cron-and-systemd\u002F","Running a CLI on a schedule with cron and systemd",[1405,1406,1407],"style",{},"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 .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 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 .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}",{"title":64,"searchDepth":77,"depth":77,"links":1409},[1410,1411,1412,1413,1414,1415,1416,1417,1424],{"id":27,"depth":77,"text":28},{"id":56,"depth":77,"text":57},{"id":253,"depth":77,"text":254},{"id":764,"depth":77,"text":765},{"id":911,"depth":77,"text":912},{"id":988,"depth":77,"text":989},{"id":1306,"depth":77,"text":1307},{"id":1320,"depth":77,"text":1321,"children":1418},[1419,1420,1421,1422,1423],{"id":1325,"depth":83,"text":1326},{"id":1336,"depth":83,"text":1337},{"id":1343,"depth":83,"text":1344},{"id":1350,"depth":83,"text":1351},{"id":1357,"depth":83,"text":1358},{"id":1371,"depth":77,"text":1372},"2026-10-02","Ship a Python CLI as a container image: a small, non-root Dockerfile, multi-arch builds and tags from git in GitHub Actions, provenance and SBOMs, and run-time ergonomics.","intermediate",false,"md",{},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fpublishing-a-cli-docker-image-from-ci",{"title":5,"description":1426},"project-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fpublishing-a-cli-docker-image-from-ci\u002Findex",[781,1435,1436,1437,1438],"containers","ci","github-actions","distribution","JweBW07jXJby0lvMKzt8PEcuRtxXSmUMWzp7uu34Cy0",[1441,1444,1447,1450,1453,1456,1459,1462,1465,1468,1471,1474,1477,1480,1483,1486,1489,1492,1495,1498,1501,1504,1507,1510,1513,1516,1519,1522,1525,1528,1531,1534,1537,1540,1543,1546,1549,1552,1555,1558,1561,1564,1567,1570,1573,1576,1579,1582,1585,1588,1591,1594,1597,1600,1603,1606,1609,1612,1615,1618,1621,1624,1627,1630,1633,1636,1639,1642,1645,1648,1651,1654,1657,1660,1663,1666,1669,1672,1675,1678,1681,1684,1687,1690,1693,1696,1699,1702,1705,1708,1711,1714,1717,1720,1723,1726,1729,1732,1735,1738,1741,1744,1747,1750,1753,1756,1759,1762,1765,1768,1771,1774,1777,1780,1783,1786,1789,1792,1795,1798,1801,1804,1807,1810,1813,1816,1819,1822,1825,1828,1831,1834,1837,1840,1843,1846,1849,1852,1855,1858,1861,1864,1867,1870,1873,1876,1879,1882,1885,1888,1891,1894,1897,1900,1903,1906,1909,1912,1915,1918,1921,1924,1927,1930,1933,1936,1939,1942,1945,1948,1951,1954,1957,1960,1963,1966,1969,1972,1975,1978,1981,1984,1987,1990,1993,1996,1999,2002,2005,2008,2011,2014,2017,2020,2023,2026,2029,2032,2035,2038,2041,2044,2047,2050,2053,2056,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,2213,2216,2219,2222,2225,2228,2231,2234,2237,2240,2243,2246,2249,2252,2255,2258,2261,2264,2267,2270,2273,2276,2279,2282],{"path":1442,"title":1443},"\u002Fabout","About Python CLI Toolcraft",{"path":1445,"title":1446},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies","Advanced Argument Validation Strategies",{"path":1448,"title":1449},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fparsing-nested-json-arguments-in-python-clis","Parsing Nested JSON Args in Python CLIs",{"path":1451,"title":1452},"\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":1454,"title":1455},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-dependent-and-conflicting-options","Validating Dependent and Conflicting CLI Options",{"path":1457,"title":1458},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-file-and-directory-paths-in-clis","Validating File and Directory Paths in CLIs",{"path":1460,"title":1461},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fvalidating-urls-hosts-and-ports","Validating URLs, Hosts and Ports in Python CLI Arguments",{"path":1463,"title":1464},"\u002Fadvanced-input-parsing-user-experience\u002Fadvanced-argument-validation-strategies\u002Fwriting-custom-click-parameter-types","Writing Custom Click Parameter Types",{"path":1466,"title":1467},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fbrowsing-records-with-a-textual-datatable","Browsing Records with a Textual DataTable Picker",{"path":1469,"title":1470},"\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":1472,"title":1473},"\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":1475,"title":1476},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual","Building Terminal UIs with Textual for Python CLIs",{"path":1478,"title":1479},"\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":1481,"title":1482},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Fstyling-textual-apps-with-tcss","Styling Textual Apps with TCSS",{"path":1484,"title":1485},"\u002Fadvanced-input-parsing-user-experience\u002Fbuilding-terminal-uis-with-textual\u002Ftesting-textual-apps-with-pilot","Testing Textual Apps with Pilot",{"path":1487,"title":1488},"\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":1490,"title":1491},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fdocumenting-environment-variables-in-help","Documenting Environment Variables in CLI Help",{"path":1493,"title":1494},"\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":1496,"title":1497},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation","CLI Help Output and Documentation",{"path":1499,"title":1500},"\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":1502,"title":1503},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fversioning-and-deprecating-cli-flags","Versioning and Deprecating CLI Flags",{"path":1505,"title":1506},"\u002Fadvanced-input-parsing-user-experience\u002Fcli-help-output-and-documentation\u002Fwriting-help-text-users-actually-read","Writing Help Text Users Actually Read",{"path":1508,"title":1509},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fadapting-output-to-terminal-width","Adapting Python CLI Output to Terminal Width",{"path":1511,"title":1512},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fdetecting-ci-environments-and-non-interactive-shells","Detecting CI Environments and Non-Interactive Shells",{"path":1514,"title":1515},"\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":1517,"title":1518},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility\u002Fhandling-ansi-escape-codes-on-windows-consoles","Handling ANSI Escape Codes on Windows Consoles",{"path":1520,"title":1521},"\u002Fadvanced-input-parsing-user-experience\u002Fcross-platform-terminal-compatibility","Cross-Platform Terminal Compatibility for Python CLIs",{"path":1523,"title":1524},"\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":1526,"title":1527},"\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":1529,"title":1530},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fchoosing-exit-codes-for-cli-tools","Choosing Exit Codes for CLI Tools",{"path":1532,"title":1533},"\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":1535,"title":1536},"\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":1538,"title":1539},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Ffriendly-error-messages-and-tracebacks","Friendly Error Messages and Tracebacks",{"path":1541,"title":1542},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fhandling-keyboard-interrupt-cleanly","Handling Keyboard Interrupt Cleanly",{"path":1544,"title":1545},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes","Error Handling and Exit Codes for CLIs",{"path":1547,"title":1548},"\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":1550,"title":1551},"\u002Fadvanced-input-parsing-user-experience\u002Ferror-handling-and-exit-codes\u002Fwriting-crash-reports-users-can-send","Writing Crash Reports Users Can Send",{"path":1553,"title":1554},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Fconfig-precedence-flags-env-files-defaults","Config Precedence: Flags, Env, Files, Defaults",{"path":1556,"title":1557},"\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":1559,"title":1560},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars","Handling Config Files and Env Vars in CLIs",{"path":1562,"title":1563},"\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":1565,"title":1566},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Freading-toml-config-with-tomllib","Reading TOML Config with tomllib in Python CLIs",{"path":1568,"title":1569},"\u002Fadvanced-input-parsing-user-experience\u002Fhandling-configuration-files-env-vars\u002Ftyped-settings-with-pydantic-settings","Typed Settings with pydantic-settings in Python CLIs",{"path":1571,"title":1572},"\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":1574,"title":1575},"\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":1577,"title":1578},"\u002Fadvanced-input-parsing-user-experience","Advanced Input Parsing for Python CLIs",{"path":1580,"title":1581},"\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":1583,"title":1584},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Fbuilding-interactive-prompts-and-menus","Building Interactive Prompts and Menus in Python CLIs",{"path":1586,"title":1587},"\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":1589,"title":1590},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich","Interactive Terminal UI with Rich",{"path":1592,"title":1593},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Flive-dashboards-with-rich-live","Live Dashboards with Rich Live in Python CLIs",{"path":1595,"title":1596},"\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":1598,"title":1599},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Frendering-tables-and-json-with-rich","Rendering Tables and JSON with Rich",{"path":1601,"title":1602},"\u002Fadvanced-input-parsing-user-experience\u002Finteractive-terminal-ui-with-rich\u002Ftheming-rich-output-consistently","Theming Rich Output Consistently in Python CLIs",{"path":1604,"title":1605},"\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":1607,"title":1608},"\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":1610,"title":1611},"\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":1613,"title":1614},"\u002Fadvanced-input-parsing-user-experience\u002Foutput-formats-for-data-clis","Output Formats for Data-Heavy Python CLIs",{"path":1616,"title":1617},"\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":1619,"title":1620},"\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":1622,"title":1623},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fargcomplete-for-argparse-clis","Tab Completion for argparse CLIs with argcomplete",{"path":1625,"title":1626},"\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":1628,"title":1629},"\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":1631,"title":1632},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis","Shell Completion for Python CLIs",{"path":1634,"title":1635},"\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":1637,"title":1638},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Fshipping-completion-scripts-with-packages","Shipping Shell Completion Scripts with a Python CLI",{"path":1640,"title":1641},"\u002Fadvanced-input-parsing-user-experience\u002Fshell-completion-for-python-clis\u002Ftesting-shell-completion-in-python-clis","Testing Shell Completion in Python CLIs",{"path":1643,"title":1644},"\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":1646,"title":1647},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fadding-verbose-and-quiet-logging-flags","Adding Verbose and Quiet Logging Flags",{"path":1649,"title":1650},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps","Structured Logging for CLI Apps",{"path":1652,"title":1653},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Flogging-with-structlog-in-a-cli","Logging with structlog in a Python CLI",{"path":1655,"title":1656},"\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":1658,"title":1659},"\u002Fadvanced-input-parsing-user-experience\u002Fstructured-logging-for-cli-apps\u002Fstructured-json-logging-in-python-clis","Structured JSON Logging in Python CLIs",{"path":1661,"title":1662},"\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":1664,"title":1665},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fdetecting-tty-and-adapting-output","Detecting a TTY and Adapting Output",{"path":1667,"title":1668},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Femitting-json-output-for-scripting","Emitting JSON Output for Scripting",{"path":1670,"title":1671},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Fhandling-broken-pipe-and-sigpipe","Handling Broken Pipe and SIGPIPE",{"path":1673,"title":1674},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes","Working with stdin, stdout and Pipes",{"path":1676,"title":1677},"\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":1679,"title":1680},"\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":1682,"title":1683},"\u002Fadvanced-input-parsing-user-experience\u002Fworking-with-stdin-stdout-and-pipes\u002Freading-piped-input-in-python-clis","Reading Piped Input in Python CLIs",{"path":1685,"title":1686},"\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":1688,"title":1689},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fdownloading-files-with-progress-in-python","Downloading Files with Progress in Python CLIs",{"path":1691,"title":1692},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis","Calling HTTP APIs from Python CLIs",{"path":1694,"title":1695},"\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":1697,"title":1698},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Foauth-device-flow-login-for-clis","OAuth Device Flow Login for Python CLIs",{"path":1700,"title":1701},"\u002Fcli-runtime-systems-integration\u002Fcalling-http-apis-from-python-clis\u002Fpaginating-api-results-in-a-cli","Paginating API Results in a Python CLI",{"path":1703,"title":1704},"\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":1706,"title":1707},"\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":1709,"title":1710},"\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":1712,"title":1713},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis","Concurrency and Async in Python CLIs",{"path":1715,"title":1716},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fmultiprocessing-for-cpu-bound-cli-tasks","Multiprocessing for CPU-Bound CLI Tasks",{"path":1718,"title":1719},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fparallelising-cli-work-with-thread-pools","Parallelising CLI Work with Thread Pools",{"path":1721,"title":1722},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Frate-limiting-concurrent-requests-in-clis","Rate-Limiting Concurrent Requests in Python CLIs",{"path":1724,"title":1725},"\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":1727,"title":1728},"\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":1730,"title":1731},"\u002Fcli-runtime-systems-integration\u002Fconcurrency-and-async-in-python-clis\u002Fstructured-concurrency-with-taskgroups-in-clis","Structured Concurrency with TaskGroups in Python CLIs",{"path":1733,"title":1734},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fcross-platform-paths-with-pathlib","Cross-Platform Paths with pathlib in CLIs",{"path":1736,"title":1737},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Ffile-locking-for-concurrent-cli-runs","File Locking for Concurrent CLI Runs in Python",{"path":1739,"title":1740},"\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":1742,"title":1743},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes","Filesystem Paths and Atomic Writes for CLIs",{"path":1745,"title":1746},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fsafe-temporary-files-and-directories","Safe Temporary Files and Directories in CLIs",{"path":1748,"title":1749},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fstoring-app-data-with-platformdirs","Storing CLI App Data with platformdirs",{"path":1751,"title":1752},"\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":1754,"title":1755},"\u002Fcli-runtime-systems-integration\u002Ffilesystem-paths-and-atomic-writes\u002Fwriting-files-atomically-in-python-clis","Writing Files Atomically in Python CLIs",{"path":1757,"title":1758},"\u002Fcli-runtime-systems-integration","CLI Runtime & Systems Integration for Python",{"path":1760,"title":1761},"\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":1763,"title":1764},"\u002Fcli-runtime-systems-integration\u002Flocal-state-and-sqlite-in-python-clis","Local State and SQLite in Python CLIs",{"path":1766,"title":1767},"\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":1769,"title":1770},"\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":1772,"title":1773},"\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":1775,"title":1776},"\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":1778,"title":1779},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Fhandling-sigterm-and-graceful-shutdown","Handling SIGTERM and Graceful Shutdown in CLIs",{"path":1781,"title":1782},"\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":1784,"title":1785},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis","Long-Running and Watch-Mode Python CLIs",{"path":1787,"title":1788},"\u002Fcli-runtime-systems-integration\u002Flong-running-and-watch-mode-clis\u002Freloading-config-on-sighup","Reloading Configuration on SIGHUP in a Python CLI",{"path":1790,"title":1791},"\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":1793,"title":1794},"\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":1796,"title":1797},"\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":1799,"title":1800},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Favoiding-shell-injection-in-python-clis","Avoiding Shell Injection in Python CLIs",{"path":1802,"title":1803},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fcalling-external-commands-safely-with-subprocess","Calling External Commands Safely with subprocess",{"path":1805,"title":1806},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fhandling-subprocess-timeouts-and-exit-codes","Handling Subprocess Timeouts and Exit Codes",{"path":1808,"title":1809},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis","Running Subprocesses from Python CLIs",{"path":1811,"title":1812},"\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":1814,"title":1815},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fpiping-between-subprocesses-in-python","Piping Between Subprocesses in Python Without a Shell",{"path":1817,"title":1818},"\u002Fcli-runtime-systems-integration\u002Frunning-subprocesses-from-python-clis\u002Fstreaming-subprocess-output-in-real-time","Streaming Subprocess Output in Real Time",{"path":1820,"title":1821},"\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":1823,"title":1824},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis","Secrets and Credentials in Python CLIs",{"path":1826,"title":1827},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fprompting-for-passwords-securely","Prompting for Passwords Securely in Python CLIs",{"path":1829,"title":1830},"\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":1832,"title":1833},"\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":1835,"title":1836},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Frefreshing-expired-tokens-automatically","Refreshing Expired Tokens Automatically in a Python CLI",{"path":1838,"title":1839},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fstoring-tokens-with-keyring","Storing CLI Tokens Securely with keyring",{"path":1841,"title":1842},"\u002Fcli-runtime-systems-integration\u002Fsecrets-and-credentials-in-python-clis\u002Fsupporting-multiple-profiles-and-accounts","Supporting Multiple Profiles and Accounts in CLIs",{"path":1844,"title":1845},"\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":1847,"title":1848},"\u002Fcli-runtime-systems-integration\u002Fupdate-checks-and-self-updating-clis","Update Checks, Upgrade Commands and Telemetry for Python CLIs",{"path":1850,"title":1851},"\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":1853,"title":1854},"\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":1856,"title":1857},"\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":1859,"title":1860},"\u002F","Python CLI Toolcraft",{"path":1862,"title":1863},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cleo","Building a Python CLI with Cleo Command Classes",{"path":1865,"title":1866},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fbuilding-a-cli-with-cyclopts","Building a Type-Hinted Python CLI with Cyclopts",{"path":1868,"title":1869},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks","Beyond Click and Typer: Alternative Python CLI Frameworks",{"path":1871,"title":1872},"\u002Fmodern-python-cli-frameworks-architecture\u002Falternative-python-cli-frameworks\u002Fquick-clis-from-functions-with-python-fire","Quick CLIs from Functions with Python Fire",{"path":1874,"title":1875},"\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":1877,"title":1878},"\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":1880,"title":1881},"\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":1883,"title":1884},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fguarding-startup-with-import-tests","Guarding CLI Startup with Import Tests",{"path":1886,"title":1887},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading","CLI Startup Performance and Lazy Loading",{"path":1889,"title":1890},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Flazy-loading-subcommands-for-faster-startup","Lazy Loading Subcommands for Faster Startup",{"path":1892,"title":1893},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Fprofiling-python-cli-startup-time","Profiling Python CLI Startup Time",{"path":1895,"title":1896},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcli-startup-performance-and-lazy-loading\u002Freducing-cli-dependency-weight","Reducing CLI Dependency Weight",{"path":1898,"title":1899},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-subparsers-for-subcommands","argparse Subparsers for Subcommands",{"path":1901,"title":1902},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fargparse-vs-click-vs-typer-comparison","argparse vs Click vs Typer Compared",{"path":1904,"title":1905},"\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":1907,"title":1908},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse","Command-Line Parsing with argparse",{"path":1910,"title":1911},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmigrating-from-argparse-to-typer","Migrating from argparse to Typer",{"path":1913,"title":1914},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fmutually-exclusive-options-in-argparse","Mutually Exclusive Options in argparse",{"path":1916,"title":1917},"\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":1919,"title":1920},"\u002Fmodern-python-cli-frameworks-architecture\u002Fcommand-line-parsing-with-argparse\u002Fwriting-custom-argparse-actions","Writing Custom argparse Actions in Python",{"path":1922,"title":1923},"\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":1925,"title":1926},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fdesigning-idempotent-commands","Designing Idempotent Commands in a Python CLI",{"path":1928,"title":1929},"\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":1931,"title":1932},"\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":1934,"title":1935},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions","Designing CLI Interfaces and Conventions in Python",{"path":1937,"title":1938},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fnaming-commands-and-flags-consistently","Naming Commands and Flags Consistently in Python CLIs",{"path":1940,"title":1941},"\u002Fmodern-python-cli-frameworks-architecture\u002Fdesigning-cli-interfaces-and-conventions\u002Fpositional-arguments-vs-options","Positional Arguments vs Options: Designing a CLI Signature",{"path":1943,"title":1944},"\u002Fmodern-python-cli-frameworks-architecture","Python CLI Frameworks and Architecture",{"path":1946,"title":1947},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fdiscovering-plugins-with-entry-points","Discovering Plugins with Entry Points in Python CLIs",{"path":1949,"title":1950},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fhook-based-plugins-with-pluggy","Hook-Based Plugins for Python CLIs with pluggy",{"path":1952,"title":1953},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis","Plugin Architectures for Extensible CLIs",{"path":1955,"title":1956},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fisolating-plugin-failures","Isolating Plugin Failures in an Extensible Python CLI",{"path":1958,"title":1959},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Ftesting-plugins-against-the-host-cli","Testing Plugins Against the Host CLI",{"path":1961,"title":1962},"\u002Fmodern-python-cli-frameworks-architecture\u002Fplugin-architectures-for-extensible-clis\u002Fversioning-a-plugin-api","Versioning a Plugin API for a Python CLI",{"path":1964,"title":1965},"\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":1967,"title":1968},"\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":1970,"title":1971},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fdependency-injection-patterns-for-cli-commands","Dependency Injection Patterns for CLI Commands",{"path":1973,"title":1974},"\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":1976,"title":1977},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis","Structuring Multi-Command Python CLIs",{"path":1979,"title":1980},"\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":1982,"title":1983},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fregistering-commands-from-modules-automatically","Registering CLI Commands from Modules Automatically",{"path":1985,"title":1986},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-common-options-across-commands","Sharing Common Options Across Python CLI Commands",{"path":1988,"title":1989},"\u002Fmodern-python-cli-frameworks-architecture\u002Fstructuring-multi-command-python-clis\u002Fsharing-state-with-click-context-objects","Sharing State with Click Context Objects",{"path":1991,"title":1992},"\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":1994,"title":1995},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications","Testing Python CLI Applications",{"path":1997,"title":1998},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fmeasuring-cli-test-coverage","Measuring CLI Test Coverage",{"path":2000,"title":2001},"\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":2003,"title":2004},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fproperty-based-testing-cli-arguments-with-hypothesis","Property-Based Testing CLI Arguments with Hypothesis",{"path":2006,"title":2007},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Fsnapshot-testing-cli-output","Snapshot Testing CLI Output",{"path":2009,"title":2010},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-click-commands-with-clirunner","Testing Click Commands with CliRunner",{"path":2012,"title":2013},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-commands-that-call-subprocesses","Testing Python CLI Commands That Call Subprocesses",{"path":2015,"title":2016},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftesting-interactive-prompts-and-stdin","Testing Interactive Prompts and stdin",{"path":2018,"title":2019},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftesting-python-cli-applications\u002Ftranscript-tests-for-cli-commands","Transcript Tests for Python CLI Commands",{"path":2021,"title":2022},"\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":2024,"title":2025},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fbuilding-dynamic-commands-in-click","Building Dynamic Commands in Click",{"path":2027,"title":2028},"\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":2030,"title":2031},"\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":2033,"title":2034},"\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":2036,"title":2037},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each","Typer vs Click: When to Use Each",{"path":2039,"title":2040},"\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":2042,"title":2043},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Ftyper-callback-functions-explained","Typer callback functions explained",{"path":2045,"title":2046},"\u002Fmodern-python-cli-frameworks-architecture\u002Ftyper-vs-click-when-to-use-each\u002Fusing-annotated-options-in-typer","Using Annotated Options in Typer",{"path":2048,"title":2049},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fautomating-releases-from-git-tags","Automating Python CLI Releases from Git Tags",{"path":2051,"title":2052},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis\u002Fcaching-uv-dependencies-in-ci","Caching uv Dependencies in CI for Python CLIs",{"path":2054,"title":2055},"\u002Fproject-setup-dependency-management\u002Fci-cd-pipelines-for-python-clis","CI\u002FCD Pipelines for Python CLIs",{"path":1431,"title":5},{"path":2058,"title":2059},"\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":2061,"title":2062},"\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":2064,"title":2065},"\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":2067,"title":2068},"\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":2070,"title":2071},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fbuilding-a-cookiecutter-template-for-typer-clis","Building a Cookiecutter Template for Typer CLIs",{"path":2073,"title":2074},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fcopier-vs-cookiecutter-for-cli-templates","Copier vs Cookiecutter for CLI Templates",{"path":2076,"title":2077},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter","CLI Project Scaffolding with Cookiecutter",{"path":2079,"title":2080},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fpost-generation-hooks-in-cli-templates","Post-Generation Hooks in Python CLI Templates",{"path":2082,"title":2083},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftemplate-variables-and-conditional-files","Template Variables and Conditional Files in CLI Templates",{"path":2085,"title":2086},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Ftesting-a-project-template-with-pytest","Testing a CLI Project Template with pytest",{"path":2088,"title":2089},"\u002Fproject-setup-dependency-management\u002Fcli-project-scaffolding-with-cookiecutter\u002Fupdating-generated-projects-with-copier-update","Updating Generated CLI Projects with copier update",{"path":2091,"title":2092},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbuilding-cross-platform-release-binaries-in-ci","Building Cross-Platform Release Binaries in CI",{"path":2094,"title":2095},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fbundling-a-python-cli-with-pyinstaller","Bundling a Python CLI with PyInstaller",{"path":2097,"title":2098},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fcode-signing-and-notarizing-cli-binaries","Code Signing and Notarizing Python CLI Binaries",{"path":2100,"title":2101},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fhomebrew-and-scoop-packaging-for-python-clis","Homebrew and Scoop Packaging for Python CLIs",{"path":2103,"title":2104},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries","Distributing CLIs as Standalone Binaries",{"path":2106,"title":2107},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Fnuitka-vs-pyinstaller-for-python-clis","Nuitka vs PyInstaller for Python CLI Binaries",{"path":2109,"title":2110},"\u002Fproject-setup-dependency-management\u002Fdistributing-clis-as-standalone-binaries\u002Freducing-pyinstaller-binary-size","Reducing the Size of a PyInstaller CLI Binary",{"path":2112,"title":2113},"\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":2115,"title":2116},"\u002Fproject-setup-dependency-management","Project Setup & Dependency Management",{"path":2118,"title":2119},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code\u002Fconfiguring-ruff-for-a-cli-project","Configuring Ruff for a Python CLI Project",{"path":2121,"title":2122},"\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":2124,"title":2125},"\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":2127,"title":2128},"\u002Fproject-setup-dependency-management\u002Flinting-and-type-checking-cli-code","Linting and Type-Checking Python CLI Code",{"path":2130,"title":2131},"\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":2133,"title":2134},"\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":2136,"title":2137},"\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":2139,"title":2140},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fautomating-changelogs-with-conventional-commits","Automating Changelogs with Conventional Commits",{"path":2142,"title":2143},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fbumping-versions-consistently-across-a-cli-project","Bumping Versions Consistently Across a Python CLI Project",{"path":2145,"title":2146},"\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":2148,"title":2149},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fexposing-version-info-and-build-metadata","Exposing Version Info and Build Metadata",{"path":2151,"title":2152},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs","Managing CLI Versioning & Changelogs",{"path":2154,"title":2155},"\u002Fproject-setup-dependency-management\u002Fmanaging-cli-versioning-changelogs\u002Fsemantic-versioning-policy-for-cli-tools","A Semantic Versioning Policy for CLI Tools",{"path":2157,"title":2158},"\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":2160,"title":2161},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbuilding-wheels-and-sdists-for-python-clis","Building Wheels and sdists for Python CLIs",{"path":2163,"title":2164},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fbundling-data-files-with-importlib-resources","Bundling Data Files with importlib.resources in CLIs",{"path":2166,"title":2167},"\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":2169,"title":2170},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution","Packaging Python CLIs for Distribution",{"path":2172,"title":2173},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Finstalling-and-distributing-clis-with-pipx","Installing and Distributing CLIs with pipx",{"path":2175,"title":2176},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Foptional-dependencies-and-extras-for-clis","Optional Dependencies and Extras for Python CLIs",{"path":2178,"title":2179},"\u002Fproject-setup-dependency-management\u002Fpackaging-python-clis-for-distribution\u002Fpublishing-a-python-cli-to-pypi","Publishing a Python CLI to PyPI",{"path":2181,"title":2182},"\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":2184,"title":2185},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fdynamic-versioning-with-poetry-plugins","Dynamic Versioning for a Poetry CLI from Git Tags",{"path":2187,"title":2188},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development","Poetry Workflows for CLI Development",{"path":2190,"title":2191},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fmanaging-poetry-lock-files-for-cli-tools","Managing Poetry Lock Files for CLI Tools",{"path":2193,"title":2194},"\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":2196,"title":2197},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-dependency-groups-for-cli-tooling","Poetry Dependency Groups for CLI Tooling",{"path":2199,"title":2200},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpoetry-entry-points-and-scripts-for-clis","Poetry Entry Points and Scripts for CLIs",{"path":2202,"title":2203},"\u002Fproject-setup-dependency-management\u002Fpoetry-workflows-for-cli-development\u002Fpublishing-a-cli-with-poetry","Building and Publishing a Python CLI with Poetry",{"path":2205,"title":2206},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects","Pre-commit Hooks for CLI Projects",{"path":2208,"title":2209},"\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":2211,"title":2212},"\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":2214,"title":2215},"\u002Fproject-setup-dependency-management\u002Fpre-commit-hooks-for-cli-projects\u002Fsetting-up-pre-commit-for-python-cli-repos","Setting up pre-commit for Python CLI repos",{"path":2217,"title":2218},"\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":2220,"title":2221},"\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":2223,"title":2224},"\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":2226,"title":2227},"\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":2229,"title":2230},"\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":2232,"title":2233},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain","Securing the Supply Chain of a Python CLI",{"path":2235,"title":2236},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpinning-dependencies-with-hashes","Pinning a Python CLI’s Dependencies with Hashes",{"path":2238,"title":2239},"\u002Fproject-setup-dependency-management\u002Fsecuring-a-python-cli-supply-chain\u002Fpublishing-attestations-and-verifying-releases","Publishing Attestations and Verifying Python CLI Releases",{"path":2241,"title":2242},"\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":2244,"title":2245},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management","uv for Python CLI Dependency Management",{"path":2247,"title":2248},"\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":2250,"title":2251},"\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":2253,"title":2254},"\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":2256,"title":2257},"\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":2259,"title":2260},"\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":2262,"title":2263},"\u002Fproject-setup-dependency-management\u002Fuv-for-python-cli-dependency-management\u002Fuv-workspaces-for-multi-package-clis","uv Workspaces for Multi-Package Python CLIs",{"path":2265,"title":2266},"\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":2268,"title":2269},"\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":2271,"title":2272},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices","Python CLI Env Isolation Best Practices",{"path":2274,"title":2275},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fisolating-cli-tools-from-project-dependencies","Isolating CLI Tools from Your Project’s Dependencies",{"path":2277,"title":2278},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fmanaging-virtual-environments-for-cross-platform-clis","Managing Python CLI Virtual Environments",{"path":2280,"title":2281},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fpinning-the-python-version-for-a-cli","Pinning the Python Version for a CLI",{"path":2283,"title":2284},"\u002Fproject-setup-dependency-management\u002Fvirtual-environments-isolation-best-practices\u002Fsupporting-multiple-python-versions-with-nox","Supporting Multiple Python Versions with nox",1790967542144]