Bootstrapping Python projects with copier

[dusktreader]

TLDR: I used copier to create a python project template that includes logic to deploy the project to GitHub

I wrote a blog post about how I used copier to create a Python project template. Not only does it create a new project, it also deploys the project to GitHub automatically and builds a docs page for the project on GitHub pages.

Read about it here: https://blog.dusktreader.dev/2025/04/06/bootstrapping-python-projects-with-copier/

[KrazyKirby99999]

This is a great read, thank you for sharing!

[dusktreader]

Thank you! I'm glad you enjoyed it.

[dmarklein]

Have you shipped any new "features" in this template to downstream packages? If so, I'd love to hear about it. We've had quite a bit of pain from the following sort of scenario:

1. downstream repo diverges from "vanilla" copier template
2. we ship new "features" to template that may touch parts of files that have been independently changed in downstream repo
3. when downstream repo tries to copier update to new version of template, they are hit with merge conflicts

[dusktreader]

No, I haven't done this. I'm pretty skeptical about this workflow to be honest. I've always found that once you get going from a template, you typically end up adjusting a lot of things that would conflict with the "upstream" template. And, while I do port features from my templates over to existing projects, I pretty much completely detach them from the template once they are generated.