Assuming that dependencies will be available on a user's system (cmemcache for example) is a sure way to lose users. An application should contain it's dependencies and not rely that they be installed on the system. BTW cmemcache has been abandoned and can no longer be compiled with current versions of memcache, libmemcache, and gcc so it's impossible to install ReviewBoard using the dependencies currently available in repos.
Our installer installs most of the dependencies users need (via easy_install). The cmemcache thing is interesting, so I'm going to repurpose this bug for that.
+ cmemcache is unmaintained?
See also http://code.djangoproject.com/ticket/12427 We're dependent on Django for this. We will want to doc it, though, when Django updates their support (and bump our required version).
+ Milestone-Release1.0.x + Component-Docs
I've been suffering by the cmemcache problem for quite a long time. It just kept complaining about this kind of errors for ever: mcm_storage_cmd():3339: unable to store value: Operation now in progress: add And then one python process (w/ lighttpd) or httpd process (w/ Apache) hangs. It seems that I just figured a way to fix (or workaround) this. As chipx86 pointed out, cmemcache isn't Review Board's dependency but Django's. The simplest way would be removing cmemcache (or don't install it at all), but install the python-memcache package instead. Django requires either of the two.
We'll update the docs and dependencies for python-memcache.
Fixed on release-1.0.x (99eb42b) and master (3ecd979). The upcoming 1.0.9 and 1.5 beta 3 versions will depend on this out of the box. For now, the docs have been updated, and will be part of tomorrow's documentation cycle.
- Confirmed + Fixed