Welcome, guest | Sign In | My Account | Store | Cart

Notice! PyPM is being replaced with the ActiveState Platform, which enhances PyPM’s build and deploy capabilities. Create your free Platform account to download ActivePython or customize Python with the packages you require and get automatic updates.

pypm install bda.cache

How to install bda.cache

  1. Download and install ActivePython
  2. Open Command Prompt
  3. Type pypm install bda.cache
 Python 2.7Python 3.2Python 3.3
Windows (32-bit)
1.1.3 Available View build log
Windows (64-bit)
1.1.3 Available View build log
Mac OS X (10.5+)
1.1.3 Available View build log
Linux (32-bit)
1.1.3 Available View build log
Linux (64-bit)
1.1.3 Available View build log
GPL: GNU General Public Licence
Lastest release
version 1.1.3 on Jan 5th, 2011

This package is designed to be used by applications which require different kinds of caching flavour. This is abstracted due to the interfaces ICacheProvider and ICacheManager. ICacheProvider takes care of the concrete cache implementation, ICacheManager is the read/write interface.

The convention is to adapt a concrete ICacheProvider implementation.

>>> from bda.cache import ICacheManager
>>> from bda.cache import Memcached
>>> provider = Memcached([''])
>>> manager = ICacheManager(provider)

We can ask the manager for data inside the cache

>>> data = manager.get('somekey', force_reload=False)

If force_reload is set to True, try to delete data with key from cache and return None.

We're also able to manipulate the cache's data (some restrictions my result out of backend not providing them)

>>> manager.set('somekey', object())

There exist a convenience to use some API's and cache it's results all at once.

>>> data = manager.getData(func, key, force_reload=False, args=[], kwargs={})

First the data for key is looked up inside the cache provider. If not found there or if force_reload is set to True, call given func . The return value of this function will be stored in the cache provider. args and kwargs are passed as parameters to given function if it's call is required.

You might ask why all this is done due to 2 seperate interfaces...

Some usecase might require different cache providers i.e. for different payload size. This way you can implement any other cache provider usage as well due to the cache manager interface.


  • zope.interface
  • zope.component
  • bda.cache.fscache.FSCache recommends that availability of cpickle
  • bda.cache.memcached.Memcached requires python-memcached


If you're interessted to contribute; Feel free but keep in mind that this code is planned to be released under a BSD like licence in future.


  • 1.1.3 (jensens, 2009-12-16)
  • reduced dependencies and tested for use in repoze.bfg
  • 1.1.2 (rnix, 2009-02-10)
  • remove legacy code
  • 1.1.1 (rnix, 2009-02-10)
  • bugfix in zcml configuration.
  • 1.1 (rnix, 2009-02-09):
  • Cache Managers are now adapters.
  • Implement memcached server support
  • deprecate the default CacheManager
  • Fix tests for FSCache
  • <= 1.0 (rnix):
  • Initial work

Subscribe to package updates

Last updated Jan 5th, 2011

Download Stats

Last month:1

What does the lock icon mean?

Builds marked with a lock icon are only available via PyPM to users with a current ActivePython Business Edition subscription.

Need custom builds or support?

ActivePython Enterprise Edition guarantees priority access to technical support, indemnification, expert consulting and quality-assured language builds.

Plan on re-distributing ActivePython?

Get re-distribution rights and eliminate legal risks with ActivePython OEM Edition.