On Wed, Apr 13, 2011 at 1:37 PM, lazyant <startup.can...@gmail.com> wrote: > Hello, > > I have a small web site that was running happily with django r15883 > that I updated March 21st. > > Yesterday I upgraded to the latest version (r16025) and then I'm > getting an error that 505s my site: > > Error importing template source loader > django.template.loaders.filesystem.load_template_source: "'module' > object has no attribute 'load_template_source'" > > at /usr/lib/python2.6/dist-packages/django/template/loader.py in > find_template_loader, line 101 > > I couldn't find anything related to this in my web searches including > http://code.djangoproject.com. > > I'm running Apache 2.2 on Ubuntu 10.10, everything pretty updated. > > I just rolled back to the previous version, but just leaving this > here, I'm not even sure this is the right place. > > I checked the changes done between the two versions with svn log -r > {2011-03-20}:{2011-04-12} and these two commits are what they look as > possible candidates for this issue: > > Advanced deprecations in django.template. > ------------------------------------------------------------------------ > r15986 | russellm | 2011-04-02 04:41:26 -0400 (Sat, 02 Apr 2011) | 1 > line > > Removed support code for deprecated module-based template loaders from > debug view postmortem. > ------------------------------------------------------------------------ > r16004 | ramiro | 2011-04-02 15:03:11 -0400 (Sat, 02 Apr 2011) | 1 > line
Function-based template loader were deprecated in Django 1.2 and will be removed in 1.4. They were replaced with class a based loader API http://code.djangoproject.com/changeset/11862 You seem to be running your site against trunk, and we've started to delete the code scheduled to be removed in 1.4 a few days after the release of 1.3, the two commits you isolated are part of that. It is not clear to me if you are using a custom template loader (in such case you need to adapt it to conform to the new API), or if you have some weird Django setup problem with both old and new code. Maybe you can share tat with us once you discover what's happening? Regarding the documentation, unfortunately the documentation changes introduced together with the code changes didn't include proper markup to signal the specific modifications perfoemed nor a related section in the respective release notes. We tried to correct these omissions somewhat late during the 1.3 development cycle. The changeset is r15309 http://code.djangoproject.com/changeset/15309 and it adds the text sections Lucasz pointed you at. It was also backported to the 1.2.X branch and th 1.2.5 release included these new doc blurbs. Regards, -- Ramiro Morales -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
