Yes, with guidance from Django/Python, I am sure the error occurs there. 
Django/Pythyon presents the trace and the line number which causes the 
exception is reported to the command Line.  However, I will look again at 
that line and all lines above.

Yes, I know there is a "good" chance as the clue is that is what the error 
message says. However, the fact is the file does exist. I've used 
copy/paste to test using "ls" the existence of both the Template folder and 
the file.  "ls" can find it. OSX's Finder can find it.  It's there.

If I comment out this part of the code, the next section which works on 
another template located in the same folder also fails.  Oddly, the first 
set of commands working on a template in the same folder works.  It's just 
the "next" one.

As mentioned, a web server is not involved, so not sure how to use the 
LOGGING variable.  I will look again.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/6sZCWEER1icJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to