Just to follow up on this - general support for passing options to
memcached clients has landed on master [1], so it's now possible to enable
binary mode, pass SASL credentials and also control any other settings
using OPTIONS.
For examples, see the end of the cache arguments documentation:
htt
As it so happens, someone else ended up tackling this problem for a
different use case in https://github.com/django/django/pull/6233.
There's a small design discussion on the pull request about how to
structure OPTIONS (possibly deprecating the current behavior of pylibmc
that passes them direc
Le lundi 22 février 2016 13:00:31 UTC+1, Ed Morley a écrit :
>
> (...)
>
> I'm happy to put together a PR to make the impact/complexity easier to
> judge, if that helps?
>
>
Yes, it always help to see the code.
> Before I do that I would just need to know whether the `username`,
> `password`
Hi Tim,
Thank you for your reply.
Yeah I spotted that discussion (it's [6] in the OP). Back then Heroku (and
other PaaS providers) were less common (and I'm not sure how many of those
users frequent this list).
Given that django-pylibmc has 8000 downloads a month on PyPI (and this is
bearing
I found an old discussion about it, but it didn't attract much interest at
the time:
https://groups.google.com/d/topic/django-developers/pISp20wuu0E/discussion
On Saturday, January 30, 2016 at 7:21:49 PM UTC-5, Ed Morley wrote:
>
> Hi
>
> For apps running on Heroku, two of the main memcached opt
Hi
For apps running on Heroku, two of the main memcached options are
MemCachier and Memcached Cloud [1]. Both of these control access via SASL
authentication, which isn't supported by Django's current pylibmc backend
[2], even though pylibmc supports it [3]. As such, currently the
django-pylibmc b
