jinja2: Don't hardcode utf-8 encoding for imported files
UTF-8 encoding for template imports was hardcoded from the beginning - from 320f29b2 (Add jinja2 "import" directive support.) Since in the previous patch we added option for input/output encoding, it makes sense to also use it, instead of hardcoding utf-8. /reviewed-by @vpelletier (on !1)
Showing
Please register or sign in to comment