Version 2 (modified by otherjacob, 5 years ago) (diff)



Tickets #12427 and #11675 are opened with different by related goals: get rid of cmemcache (which had gone the way of the broken-as-heck dodo) and add support for a new libmemcached wrapper pylibmc (respectively).

Feb 2010

Email thread seen here begins:

March 2010

Ticket is put in for 1.2 to put use of cmemcache as FuturePendingDeprecation, while adding support for pylibmc was greenlit for 1.3

October 2010

Discussion re-started with three key points to debate:

Another post of note with regards to multithreading [ala, celery] here:

November 2010

11/29: Draft one suggested to the django-dev lift Draft #1:

Caveats/Notes on the draft: A) This is only the file, changes to conf/global_settings and core/cache/base will be needed to handle the move towards CACHE_SETTINGS

B) pylibmc and memcached handle negative timeouts differently. The expected behavior as laid out in template tests is how python-memcached handles it (instant expiration). I had to do a fairly sad looking hack to make pylibmc work, and is noted in a comment.

C) The current version of pylibmc doesn't play nice with python sub-interuptors, and thus, mod_wsgi. There is a commit ( in trunk that fixes this, but a release has not been given out. We may want to be extra-communicative of this and the possible workarounds.

Back to Top