Documentation for pylibmc cache backend needs additional info

[Jay Hargis]

Looking at the docs you'd assume that this would work for socket connections to memcached via pylibmc..

CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache',
        'LOCATION': 'unix:/tmp/memcached.sock',
    }
}

but it doesn't unless you drop the unix prefix

CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache',
        'LOCATION': '/tmp/memcached.sock',
    }
}

Searching the web there is very little mention of this. Would be helpful to see the distinction in the docs.

[Tim Graham]

If you could draft a patch, I'll be happy to review it.

[Bryan Marty]

Diff:
​https://github.com/bxm156/django/commit/f1c5238266981a59d71b49e1e0ce6f7f9acf8faf

Created a pull request:
​https://github.com/django/django/pull/5515

[Tim Graham <timograham@…>]

In ad67fcdf:

Fixed #24212 -- Added example pylibmc CACHES configuration.

[Tim Graham <timograham@…>]

In dd0e7f53:

[1.8.x] Fixed #24212 -- Added example pylibmc CACHES configuration.

Backport of ad67fcdf51ebbbd7c02c1a2b1f269edc8f92afdc from master

[Tim Graham <timograham@…>]

In a09a889:

[1.9.x] Fixed #24212 -- Added example pylibmc CACHES configuration.

Backport of ad67fcdf51ebbbd7c02c1a2b1f269edc8f92afdc from master

[Mariusz Felisiak <felisiak.mariusz@…>]

In a629139:

Refs #29887, Refs #24212 -- Added servers configuration hook for memcached backends.

The servers property can be overridden to allow memcached backends to
alter the server configuration prior to it being passed to instantiate
the client. This allows avoidance of documentation for per-backend
differences, e.g. stripping the 'unix:' prefix for pylibmc.

[Mariusz Felisiak <felisiak.mariusz@…>]

In cda0a3d7:

Refs #29887, Refs #24212 -- Added more client servers tests for PyLibMCCache.