Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change to copier instead of cookie-cutter #348

Closed
abelsiqueira opened this issue Sep 8, 2023 · 2 comments
Closed

Change to copier instead of cookie-cutter #348

abelsiqueira opened this issue Sep 8, 2023 · 2 comments
Labels
copier template Related to the template itself, as opposed to the generated code

Comments

@abelsiqueira
Copy link
Member

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.

@abelsiqueira abelsiqueira added the template Related to the template itself, as opposed to the generated code label Sep 8, 2023
@egpbos
Copy link
Member

egpbos commented 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.

lyashevska added a commit that referenced this issue Jul 25, 2024
This migrates from cookiecutter template to copier while keeping all
features as they are. This was done by @sjvrijn and @lyashevska.

Closes #348
lyashevska added a commit that referenced this issue Jul 25, 2024
This migrates from cookiecutter template to copier while keeping all
original features.

Closes #348

Co-authored-by: Olga Lyashevska <olga.lyashevska@gmail.com>
Co-authored-by: Sander van Rijn <s.vanrijn@esciencecenter.nl>
lyashevska added a commit that referenced this issue Jul 26, 2024
This migrates from cookiecutter template to copier while keeping all
original features.

Closes #348

Co-authored-by: Olga Lyashevska <olga.lyashevska@gmail.com>
Co-authored-by: Sander van Rijn <s.vanrijn@esciencecenter.nl>
lyashevska added a commit that referenced this issue Jul 29, 2024
This migrates from cookiecutter template to copier while keeping all
original features.

Closes #348

Co-authored-by: Olga Lyashevska <olga.lyashevska@gmail.com>
Co-authored-by: Sander van Rijn <s.vanrijn@esciencecenter.nl>
lyashevska added a commit that referenced this issue Jul 29, 2024
This migrates from cookiecutter template to copier while keeping all
original features.

Closes #348

Co-authored-by: Olga Lyashevska <olga.lyashevska@gmail.com>
Co-authored-by: Sander van Rijn <s.vanrijn@esciencecenter.nl>
@egpbos
Copy link
Member

egpbos commented Aug 30, 2024

🥳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
copier template Related to the template itself, as opposed to the generated code
Projects
None yet
Development

No branches or pull requests

3 participants