Okay, the patch is good to go. Looking forward to seeing it in trunk! -Lau
On Jun 9, 6:43 pm, Joe Bowman <[EMAIL PROTECTED]> wrote: > That would be a big help for implementing backends for appengine. > > I did notice a project working on an appengine helper for Django > managed to also accomplish this by creating a cache middleware. So for > others on appengine currently, using the .96 version of Django > included within the environment, this is a direction you can look at > also. I imagine there will be some lag time between a stable release > of Django and adoption by appengine. > > On Jun 9, 11:44 am, Lau Bech Lauritzen <[EMAIL PROTECTED]> > wrote: > > > I created a ticket (including patch) that might be of interest: > > > http://code.djangoproject.com/ticket/7398 > > > On Jun 3, 10:10 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote: > > > > On Tue, Jun 3, 2008 at 2:58 PM, Joe Bowman <[EMAIL PROTECTED]> wrote: > > > > .... > > > > > Should I just create it and > > > > tell people to copy it into the directory with the default cache > > > > backends? That appears the only way to insert a new one, but I'm so > > > > new to Django I thought I should ask first and see if there's a > > > > preferred way. > > > > A directory there is currently the only way. > > > This line in django/core/cache/__init__.py is the culprit: > > > > cache_class = getattr(__import__('django.core.cache.backends.%s' % > > > BACKENDS[scheme], {}, {}, ['']), 'CacheClass') > > > > You could, of course, also smash the django.core.cache.cache attribute > > > with your own, if you wanted to be rude. > > > > It certainly seems to me that SESSION_ENGINE (with module pathing) is > > > a better approach than CACHE_BACKEND (with URI-ish schemes). This > > > could be overcome by allowing scheme resolution to be registered. The > > > argument for or against is a bikeshed. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
