#24646: File names jinja2.py cannot import jinja2
-------------------------------------+-------------------------------------
Reporter: Daniel Greenfeld | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: 1.8
Severity: Normal | Resolution: fixed
Keywords: jinja2 | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => fixed
Comment:
I can't reproduce a problem unless I remove the `from __future__ import
absolute_import` that the commit for this ticket added. Could you please
provide a sample project that reproduces the problem? Ideally, you would
use [wiki:TicketClosingReasons/UseSupportChannels our support channnels]
rather than this ticket tracker. Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/24646#comment:12>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.2689f314599068894ac922a5056494a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
