On Sun, Apr 18, 2010 at 3:54 AM, Michael Strickland <moriog...@gmail.com>wrote:
> Temporary fix: > > It appears to be a result of changeset [12637] in memcached.py: > http://code.djangoproject.com/changeset/12637 > > # memcached.py, lines 53-54 removed in def set() > 53: if isinstance(value, unicode): > 54: value = value.encode('utf-8') > > In my templates at least, this means that before 12637, memcached.py > converted the data from <class 'django.utils.safestring.SafeUnicode'> > to <class 'django.utils.safestring.SafeString> before saving it. It no > longer does this conversion, which appears to be necessary at least > for some users. > > I was able to fix it by adding those two lines back in to > memcached.py, so the data is converted before the cache attempts to > save it. > > Not to familiar with memcached - any reason it wouldn't be able to > digest the unconverted data? I can't tell if this is something that > was overlooked when 12637 was adopted, or whether Willem and I have > something wrong with our caches... > Which Python memcached bindings are you using -- cmemcached or python-memcached? Karen -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
