.. image:: https://img.shields.io/pypi/v/pymemcache.svg :target: https://pypi.python.org/pypi/pymemcache
.. image:: https://readthedocs.org/projects/pymemcache/badge/?version=master :target: https://pymemcache.readthedocs.io/en/latest/ :alt: Master Documentation Status
A comprehensive, fast, pure-Python memcached client.
pymemcache supports the following features:
Install from pip:
.. code-block:: bash
pip install pymemcache
For development, clone from github and run the tests:
.. code-block:: bash
git clone https://github.com/pinterest/pymemcache.git
cd pymemcache
Run the tests (make sure you have a local memcached server running):
.. code-block:: bash
tox
See the documentation here: https://pymemcache.readthedocs.io/en/latest/
Since version 3.2, Django has included a pymemcache-based cache backend.
See its documentation <https://docs.djangoproject.com/en/stable/topics/cache/#memcached>__.
On older Django versions, you can use
django-pymemcache <https://github.com/django-pymemcache/django-pymemcache>_.
The pylibmc library is a wrapper around libmemcached, implemented in C. It is fast, implements consistent hashing, the full memcached protocol and timeouts. It does not provide access to the "noreply" flag. It also isn't pure Python, so using it with libraries like gevent is out of the question, and its dependency on libmemcached poses challenges (e.g., it must be built against the same version of libmemcached that it will use at runtime).
The python-memcached library implements the entire memcached text protocol, has a single timeout for all socket calls and has a flexible approach to serialization and deserialization. It is also written entirely in Python, so it works well with libraries like gevent. However, it is tied to using thread locals, doesn't implement "noreply", can't treat errors as cache misses and is slower than both pylibmc and pymemcache. It is also tied to a specific method for handling clusters of memcached servers.
The team at mixpanel put together a pure Python memcached client as well. It has more fine grained support for socket timeouts, only connects to a single host. However, it doesn't support most of the memcached API (just get, set, delete and stats), doesn't support "noreply", has no serialization or deserialization support and can't treat errors as cache misses.
The memcached text protocol reference page: https://github.com/memcached/memcached/blob/master/doc/protocol.txt
The python-memcached library (another pure-Python library): https://github.com/linsomniac/python-memcached
Mixpanel's Blog post about their memcached client for Python: https://engineering.mixpanel.com/we-went-down-so-we-wrote-a-better-pure-python-memcache-client-b409a9fe07a9
Mixpanel's pure Python memcached client: https://github.com/mixpanel/memcache_client
Bye-bye python-memcached, hello pymemcache (migration guide) https://jugmac00.github.io/blog/bye-bye-python-memcached-hello-pymemcache/
Charles Gordon <http://github.com/cgordon>_Dave Dash <http://github.com/davedash>_Dan Crosta <http://github.com/dcrosta>_Julian Berman <http://github.com/Julian>_Mark Shirley <http://github.com/maspwr>_Tim Bart <http://github.com/pims>_Thomas Orozco <http://github.com/krallin>_Marc Abramowitz <http://github.com/msabramo>_Marc-Andre Courtois <http://github.com/mcourtois>_Julien Danjou <http://github.com/jd>_INADA Naoki <http://github.com/methane>_James Socol <http://github.com/jsocol>_Joshua Harlow <http://github.com/harlowja>_John Anderson <http://github.com/sontek>_Adam Chainz <http://github.com/adamchainz>_Ernest W. Durbin III <https://github.com/ewdurbin>_Remco van Oosterhout <https://github.com/Vhab>_Nicholas Charriere <https://github.com/nichochar>_Joe Gordon <https://github.com/jogo>_Jon Parise <https://github.com/jparise>_Stephen Rosen <https://github.com/sirosen>_Feras Alazzeh <https://github.com/FerasAlazzeh>_Moisés Guimarães de Medeiros <https://github.com/moisesguimaraes>_Nick Pope <https://github.com/ngnpope>_Hervé Beraud <https://github.com/4383>_Martin Jørgensen <https://github.com/martinnj>_Are you really excited about open-source? Or great software engineering?
Pinterest is hiring <https://careers.pinterest.com/>_!
#321 <https://github.com/pinterest/pymemcache/pull/321>_
#363 <https://github.com/pinterest/pymemcache/pull/363>_#407 <https://github.com/pinterest/pymemcache/pull/407>_STAT values.Client.get returns the default when using ignore_exc and if memcached
is unavailablenoreply support to HashClient.flush_all.MemcacheUnexpectedCloseError.pool_idle_timeout.HashClient.{get,set}_many() with UNIX sockets.stats. This was a violation of the memcached protocol.MemcacheIllegalInputError when None is
given as the cas value.HashClient now supports UNIX sockets.HashClient can now be imported from the top-level pymemcache package
(e.g. pymemcache.HashClient).HashClient.get_many() now longer stores False for missing keys from
unavailable clients. Instead, the result won't contain the key at all.HashClient.close() and HashClient.quit().PooledClient and HashClient now support custom Client classesMockMemcacheClient to behave even more like Clientencoding from HashClient to its pooled clients when use_pooling
is enabled.serde to be an object which implements serialize and deserialize
as methods. (serialize and deserialize are still supported but
considered deprecated.)expire, delay, incr, decr, and
memlimit -- non-integer values now raise MemcacheIllegalInputErrorcas -- values which are not integers or strings of
0-9 now raise MemcacheIllegalInputErrorprepend and append support to MockMemcacheClient.touch method to HashClient.long_description string in Python packaging.flags when setting multiple differently-typed values at once.setup.cfg metadata instead setup.py config to generate package.default_noreply parameter to HashClient.encoding parameter to Client constructors (defaults to ascii).flags parameter to write operation methods.MockMemcacheClient correctly.setup.py dependency on six already being installed.pymemcache package (e.g. pymemcache.Client).
#197 <https://github.com/pinterest/pymemcache/pull/197>_#206 <https://github.com/pinterest/pymemcache/pull/206>_cache_memlimit command.
#211 <https://github.com/pinterest/pymemcache/pull/211>_#209 <https://github.com/pinterest/pymemcache/pull/209>_#179 <https://github.com/pinterest/pymemcache/pull/179>_#187 <https://github.com/pinterest/pymemcache/pull/187>_#182 <https://github.com/pinterest/pymemcache/pull/182>_#183 <https://github.com/pinterest/pymemcache/pull/183>#184 <https://github.com/pinterest/pymemcache/pull/184>_#190 <https://github.com/pinterest/pymemcache/pull/190>_pypy3 to travis test matrix
full benchmarks in test
fix flake8 issues
Have mockmemcacheclient support non-ascii strings
Switch from using pickle format 0 to the highest available version. See #156 <https://github.com/pinterest/pymemcache/pull/156>_
Warning: different versions of python have different highest pickle versions: https://docs.python.org/3/library/pickle.html
#103 <https://github.com/pinterest/pymemcache/issues/103>_#109 <https://github.com/pinterest/pymemcache/issues/139>_#131 <https://github.com/pinterest/pymemcache/pull/131>_allow_unicode_keys when creating the clients, thanks @jogo!default_noreply arg set on init, thanks @kols!FAQs
A comprehensive, fast, pure Python memcached client
We found that pymemcache demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.