Repository navigation
Change to copier instead of cookie-cutter #348
Description
Following a discussion on Teams, we should discuss moving to copier.
The main reason for a move would be the ability to update a package when the template is updated.
However, maybe users don't actually want this. I guesstimate that many people change the template heavily after cloning it. E.g., by removing prospector or by using MkDocs instead of ReadTheDocs.
Another advantage, a side effect of the update procedure, is that the repo name will be recorded, so it will be easier to keep track of who is using the template.
My estimate of the amount of work for the update should be around 2-4 hours, except for tests, which I have no idea what they do.
Activity
egpbos commentedon Jul 5, 2024
As discussed in the first Python template team meeting, and also earlier in #348, we are considering moving to Copier. @lyashevska is looking into this as we speak, taking into account lessons learned in the CopierTemplate.jl project and also connecting with the TDCC-NES project's efforts into a similar direction.
Migrate from cookiecutter to copier
Migrate from cookiecutter to copier
Migrate from cookiecutter to copier
Migrate from cookiecutter to copier
Migrate from cookiecutter to copier
Migrate from cookiecutter to copier
egpbos commentedon Aug 30, 2024
🥳