You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2019. It is now read-only.
If a site is using Django 1.8 and does not have any TEMPLATES engine definition for Django templates (if they're using Jinja or something else instead), they'll need to add an extra engine definition specifically for our library if they want to use our helpers. We should document something to that effect.
(I have yet to actually get around to testing this, so I might be getting the details of the problem wrong.)
The text was updated successfully, but these errors were encountered:
The Django 1.8 documentation is not very clear yet on how libraries should handle custom template engines. In the meantime, the code in git now works with the DTL, and the currently released code does not work with Django 1.8 at all.
Would it be possible to cut a release with what we have now? My webapp uses django-browserid and I currently have to force users to use Django 1.7.
I'm hoping to cut a release after #289 gets merged (I wrote it in response to one of my projects using Django 1.8 and django-jinja and failing when I updated django-browserid), and then land some documentation updates.
If a site is using Django 1.8 and does not have any
TEMPLATES
engine definition for Django templates (if they're using Jinja or something else instead), they'll need to add an extra engine definition specifically for our library if they want to use our helpers. We should document something to that effect.(I have yet to actually get around to testing this, so I might be getting the details of the problem wrong.)
The text was updated successfully, but these errors were encountered: