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
Error when running translations extract with legacy Jinja2 extensions #1179
Comments
sabius
changed the title
Translations extract and legacy Jinja2 extensions
Error when running translations extract with legacy Jinja2 extensions
Sep 6, 2021
I was able to reproduce this on a project using the Blogger extension; will investigate.
|
jeremydw
added a commit
that referenced
this issue
Sep 6, 2021
Thanks for reporting this; just pushed a fix in grow Steps to fix it:
Finally, ensure you've run |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi.
After updating Grow from Python2 to 2.0.5's Python3, there's an issue with legacy extensions when running
grow translations extract
with the message:ModuleNotFoundError: No module named 'extensions'
This is when setting up custom extensions in the jinja2 key in the extensions of the podspec in the way:
A temporary workaround for the translations extract is to comment out the jinja2 node. Is there a suggested way to add legacy extensions that work with the translations extract process? Otherwise this might be an issue with the translations extract after upgrading to Python3.
Thanks.
The text was updated successfully, but these errors were encountered: