On Mar 10, 1:44 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Good point. You're right, the code in Django is only going to have the
> same thread-safety as memcache.Client (all our accesses to that object
> are atomic).
>
> This has to be fixable without too much pain, so if you could file
We encountered the same problem with the memcache client. I submitted
this patch to the memcache client maintainer, but I don't think it's
been released yet:
65c65,73
< class Client:
---
> try:
> # Only exists in Python 2.4+
> from threading import local
> except ImportError:
> # TOD
On Sat, 2007-03-10 at 13:24 -0800, Samuel wrote:
> I ran into a problem with Django's caching backend when using memcache
> and threads. Instances of memcache.Client are not thread-safe, and
> Django creates a single instance shared by all threads. I wanted to
> post this here rather than report
I ran into a problem with Django's caching backend when using memcache
and threads. Instances of memcache.Client are not thread-safe, and
Django creates a single instance shared by all threads. I wanted to
post this here rather than report a bug since it's not necessarily a
bug in Django; however
