Automate generation¶
Generate with defaults¶
uvx python-project-foundry /path/to/new/project --defaults
Defaults are derived from the destination name where possible:
/tmp/orbit-tools
├── project name: Orbit Tools
├── distribution: orbit-tools
└── import package: orbit_tools
Review the full questionnaire reference before
using defaults in automation. In particular, the GitHub owner defaults to
acme.
Preview without writing¶
uvx python-project-foundry /path/to/new/project --defaults --pretend
Render without setup tasks¶
uvx python-project-foundry /path/to/new/project --defaults --skip-tasks
This creates files but does not initialize Git, install dependencies, or install hooks. Run the desired setup later from the generated project:
make hooks-install
Existing destinations¶
| Option | Behavior |
|---|---|
| No option | Copier protects conflicting existing files |
--overwrite |
Allow generated files to replace existing files |
--pretend |
Show planned file operations only |
Warning
Preview before combining automation with --overwrite.
Custom unattended answers¶
The focused ppf CLI currently supports either interactive answers or all
defaults; it does not accept individual answer flags or a data file. For a
repeatable customized scaffold:
- generate interactively in a staging directory;
- record the answers from
.python-project-foundry.answers.yaml; - keep the generated repository as the reproducible artifact.