thanks jeremy. here´s the information: CACHE_BACKEND = 'memcached://dedhost-sil-076.sil.at:11211/'
I´m not using the cache_middleware, because I´m using the per-view- cache. Just re-checked the django-docs and hope I don´t misunderstand the whole caching-thing - but according to the docs, the cache_middleware is not necessary for the cache_page decorator. instead of sending the whole stack, it´s probably easier to just check it yourself: http://skip.dedhost-sil-076.sil.at/trailer/ thanks, patrick On Aug 29, 4:49 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote: > On 8/28/07, patrickk <[EMAIL PROTECTED]> wrote: > > > > > additional information: > > I just checked the default encoding > > > >>> import sys > > >>> sys.getdefaultencoding() > > 'ascii' > > > should that be something different (like utf-8)? > > btw: all our data (database) and scripts are encoded with utf-8. > > patrickk, I'm not sure what lapain's experience with unicode is, but > please disregard the advice to switch defaultencoding to utf-8. > Despite appearances, it's *good* that python refuses to guess what > encoding you might wish to emit. You've found a bug in Django, and > it's better to fix Django than tell everybody to go hack their python > installs or change their processes with unusual configurations. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
