memcached 1.2_tummy3

Brad Fitzpatrick brad at
Sat Apr 16 10:19:43 PDT 2005

I feel no need to be the patch maintainer and host for the Python API.
I'm actually quite happy a maintainer has forked it and hosted it
themselves... I should take down our Python module links and link to the
tummy version.

Any objections?

On Sat, 16 Apr 2005, Evan Martin wrote:

> "This is a fork of the Danga memcached module for Python. Memcached is
> a high-performance daemon which can run on multiple systems and cache
> database queries and other data to improve performance. For example,
> JOTWeb can use memcached to cache rendered pages resulting in being
> about 25% slower than Apache serving static pages when serving cached
> pages.
> This is a fork of the code written by the folks at Danga (the authors
> of memcached). The base code has some bugs in it, and is missing some
> API routines, which the tummy fork fixes/includes. Danga has not
> expressed any interest in accepting these changes, so I've forked it."
> I looked back through my mail to see if I'd heard from this guy, and
> all I have is a few short but reasonable patches and a little
> discussion about what improvements I thought would be good.  Not quite
> sure what happened, really.  (Brad, you were CC'd on all the mails,
> subject "Taking over the maintenance of the memcached Python API.")
> I'd suggest either tracking down the patches and integrating them or
> just putting up a link on the clients page.

More information about the memcached mailing list