Daymien has a similar issue at 
http://groups.google.com/group/django-users/t/7b7dad85530eceed

Just wanted to link the two discussions.

On Jul 30, 12:11 pm, chefsmart <moran.cors...@gmail.com> wrote:
> There is absolutely no difference between my dev and production, only
> the database details in the settings.py are different.
>
> The 'django.template.loaders.app_directories.load_template_source' is
> not included in both my dev as well as my production setups (which is
> in testing phase now).
>
> So since there is essentially no difference between the two setups, I
> am guessing the error is because of the pre-requisites. Sadly I don't
> know what those are to be effective in my troubleshooting.
>
> On Jul 30, 10:49 am, krylatij <kryla...@gmail.com> wrote:
>
> > And do you want to avoid
> > 'django.template.loaders.app_directories.load_template_source' ?
>
> > It will work only when your template will not be found in default
> > template directory
> > So i guess there is no overhead when you use it in production.
>
> > May be you have DEBUG=True in your development version and
> > DEBUG=False in production. So it can be the reason.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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