-
Notifications
You must be signed in to change notification settings - Fork 91
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
build: support copier 9 #221
Conversation
comment_start_string: "{#" | ||
keep_trailing_newline: true | ||
variable_end_string: "}}" | ||
variable_start_string: "{{" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yajo does this mean the default jinja syntax changed with copier 9?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It changed many versions ago. We just didn't have a constraint, so we had to define it manually.
Why forcing the latest version and why each version is incompatible with the previous? |
There are a few fixes for Copier is detached from the template, so ensuring a minimal version is used means more predictable replayability. Regarding incompatibilities, you can see the changelog. |
My fear here is that copier won't run in its latest version in all current development environments. Is it working for current + previous LTS versions of popular distros? |
AFAIK no popular distro packages copier. |
I mean the dependencies for making copier to run. If copier now depends on the library X version N that is incompatible/not found in for example Ubuntu 22.04, it's a big problem. |
If you install copier with pipx or nix, it won't be a problem. |
OK, good to know. I'll write back if any problem found. |
No description provided.