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 a > ticket, that would be great. That gives us somewhere to point people to > if they come across it before we can fix it (rule of thumb: once one > person spots this, everybody suddenly notices it). > > Thanks for pointing this out. > > Regards, > Malcolm
Here's the ticket: http://code.djangoproject.com/ticket/3701 I'm not sure what other information to add to the ticket, but it is linked back to this thread in case any discussion happens on either side. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
