#12787: TemplateDoesNotExist exception does not report the correct template_name
-------------------------------------------+--------------------------------
               Reporter:  trigeek38        |         Owner:  anonymous          
 
                 Status:  closed           |     Milestone:  1.2                
 
              Component:  Template system  |       Version:  SVN                
 
             Resolution:  fixed            |      Keywords:  
TemplateDoesNotExist
           Triage Stage:  Unreviewed       |     Has patch:  1                  
 
    Needs documentation:  0                |   Needs tests:  1                  
 
Patch needs improvement:  1                |  
-------------------------------------------+--------------------------------
Changes (by kmtracey):

  * status:  reopened => closed
  * resolution:  => fixed


Comment:

 The problem identified in this ticket was fixed, really. The fix includes
 tests, which failed before the code change and are still passing on
 current trunk:

 {{{
 ~/django/trunk/tests
 --> ./runtests.py --settings=testdb.sqlite -v2
 templates.Templates.test_extends_include_missing_baseloader
 templates.Templates.test_extends_include_missing_cachedloader
 Importing application templates
 Creating test database for alias 'default' (':memory:')...
 Creating tables ...
 Creating table django_content_type
 Creating table auth_permission
 Creating table auth_group_permissions
 Creating table auth_group
 Creating table auth_user_user_permissions
 Creating table auth_user_groups
 Creating table auth_user
 Creating table auth_message
 Creating table django_site
 Creating table django_flatpage_sites
 Creating table django_flatpage
 Creating table django_redirect
 Creating table django_session
 Creating table django_comments
 Creating table django_comment_flags
 Creating table django_admin_log
 Installing custom SQL ...
 Installing indexes ...
 No fixtures found.
 Creating test database for alias 'other' ('other_db')...
 Destroying old test database 'other'...
 Creating tables ...
 Creating table django_content_type
 Creating table auth_permission
 Creating table auth_group_permissions
 Creating table auth_group
 Creating table auth_user_user_permissions
 Creating table auth_user_groups
 Creating table auth_user
 Creating table auth_message
 Creating table django_site
 Creating table django_flatpage_sites
 Creating table django_flatpage
 Creating table django_redirect
 Creating table django_session
 Creating table django_comments
 Creating table django_comment_flags
 Creating table django_admin_log
 Installing custom SQL ...
 Installing indexes ...
 No fixtures found.
 test_extends_include_missing_baseloader
 (regressiontests.templates.tests.Templates) ... ok
 test_extends_include_missing_cachedloader
 (regressiontests.templates.tests.Templates) ... ok

 ----------------------------------------------------------------------
 Ran 2 tests in 0.004s

 OK
 Destroying test database for alias 'default' (':memory:')...
 Destroying test database for alias 'other' ('other_db')...
 }}}

 Further, if you doubt the tests, if I change one of my current projects to
 have the problem noted in the original description -- one existing
 template including a 2nd existing template that in turn attempts to
 include a 3rd template that does not exist, the debug page I get correctly
 identifies the template that is missing.

 You may be seeing a bug, but it is not this exact bug. Better than trying
 to show how the code change made here is wrong would be a test case that
 shows the case you are running into where a problem exists. And that
 should go into its own new ticket (that perhaps references this one),
 because this specific one is fixed.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/12787#comment:11>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to