pup-up: Professional Python Project Updater
Opinionated professional Python project template synchronizer
Purpose
Professional Python repositories commonly share infrastructure such as:
- editor and Git configuration
- ignore and line-ending rules
- Markdown, YAML, and link checking
- formatting, linting, type checking, and testing
- documentation tooling
- continuous integration
- package and release validation
pup-up makes it easy to keep the infrastructure files commonly used in
professional projects current and consistent.
Template Source
Update a Repo based on Templates
# see what files would change (dry run, the default)
uvx pup-up
# see what files the command would update (dry run, force latest version)
uvx pup-up@latest
# see exactly what would change, line by line
uvx pup-up --diff
# add and overwrite all the files listed (CAUTION: DESTRUCTIVE)
uvx pup-up --write
# add and overwrite only specific files listed (CAUTION: DESTRUCTIVE)
uvx pup-up --write .gitattributes .github/.yamllint.yml .github/workflows/links.yml
Developer Command Reference
Show command reference
In a machine terminal
Open a machine terminal where you want the project:
git clone https://github.com/denisecase/pup-up
cd pup-up
code .
In a VS Code terminal
uv self update
uv python pin 3.15
uv lock --upgrade
uv sync --extra dev --extra docs
uv run pre-commit install
uv run pre-commit autoupdate
git add -A
uv run pre-commit run --all-files
# repeat if changes were made
uv run pre-commit run --all-files
# run locally to test
uv run pup-up
uv run pup-up --diff
uv run pup-up --write
uv run pup-up --write .gitattributes .github/.yamllint.yml .github/workflows/links.yml
# types, tests, docs
uv run python -m pyright
uv run python -m pytest
uv run python -m zensical build
# save progress
git add -A
git commit -m "update"
git push -u origin main
Annotations
Citation
License
1 maintainer
Release files for pup-up 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pup_up-0.0.2.tar.gz | 18.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pup_up-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.4 kB
Release files / pup_up-0.0.2.tar.gz
| Download URL | pup_up-0.0.2.tar.gz |
|---|---|
| Size | 18.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ada3a2142adf72b238c288ea1d41dc442d965d3a2e714a6eb253e003404970e
|
|
BLAKE2b-256 checksum How to use checksums |
d6e55cb93d05d49c8b21df32003a4802cf4e0926c0dbe115b7c5125d842feff9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 8, 2026.
Transparency logRelease files / pup_up-0.0.2-py3-none-any.whl
| Download URL | pup_up-0.0.2-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4c6418cfaf231d0387038285cf0d0052a8f8a63e7a6f5af080884281aabf1760
|
|
BLAKE2b-256 checksum How to use checksums |
e5dae9449f17bc933d26612f1f3ed2eb2e371c2d776b434a785ae35cd68a8246
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 8, 2026.
Transparency log
