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

Jinja2 is being renamed to 'Jinja' #197

Closed
geerlingguy opened this issue Jan 15, 2020 · 3 comments
Closed

Jinja2 is being renamed to 'Jinja' #197

geerlingguy opened this issue Jan 15, 2020 · 3 comments

Comments

@geerlingguy
Copy link
Owner

@geerlingguy geerlingguy commented Jan 15, 2020

See:

In the book, there are multiple references to "Jinja2", which I should update and rename to just "Jinja".

@geerlingguy

This comment has been minimized.

Copy link
Owner Author

@geerlingguy geerlingguy commented Jan 15, 2020

One interesting side effect... all the stuff in Ansible (including my book and most of my example playbooks and such) use the .j2 extension to indicate 'Jinja2' templates... I'm probably going to leave that alone for now, since that's a more seismic change—but it looks like according to a recent docs change, the .jinja extension may be the recommended Jinja-specific file extension.

@geerlingguy

This comment has been minimized.

Copy link
Owner Author

@geerlingguy geerlingguy commented Jan 15, 2020

Fixed the plain text references, and opened a follow-up for changing file names: #199

@davidism

This comment has been minimized.

Copy link

@davidism davidism commented Jan 25, 2020

Just a heads up, since I saw this linked from the Jinja issue: We're no longer planning to rename the package or imports, they will remain jinja2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.