On Fri, May 13, 2016 at 1:12 PM, Adam Young wrote:
> On 05/13/2016 12:52 PM, Monty Taylor wrote:
>
>> On 05/13/2016 11:38 AM, Eric Larson wrote:
>>
>>> Monty Taylor writes:
>>>
>>> On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote:
> On Fri, May 13, 2016 at 02:58:08PM
On 05/13/2016 12:52 PM, Monty Taylor wrote:
On 05/13/2016 11:38 AM, Eric Larson wrote:
Monty Taylor writes:
On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote:
On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote:
What's wrong with pymemcache, that we picked for tooz and are using
for 2
On 05/13/2016 11:38 AM, Eric Larson wrote:
>
> Monty Taylor writes:
>
>> On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote:
>>> On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote:
What's wrong with pymemcache, that we picked for tooz and are using
for 2 years now?
Monty Taylor writes:
On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote:
On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote:
What's wrong with pymemcache, that we picked for tooz and are
using for 2 years now?
https://github.com/pinterest/pymemcache
Looks like a good alternative.
On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote:
> On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote:
>> What's wrong with pymemcache, that we picked for tooz and are using for
>> 2 years now?
>>
>> https://github.com/pinterest/pymemcache
>
> Looks like a good alternative.
Honestly,
On Fri, May 13, 2016 at 6:23 AM, Mehdi Abaakouk wrote:
> On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote:
>
>> What's wrong with pymemcache, that we picked for tooz and are using for
>> 2 years now?
>>
>> https://github.com/pinterest/pymemcache
>>
>
> Looks like
On 13 May 2016, at 1:14, Steve Martinelli wrote:
> /me gets the ball rolling
>
> Just when python3 support for keystone was looking like a reality, we've
> hit another snag. Apparently there are several issues with python-memcached
> in py3, putting it simply: it loads, but doesn't actually
On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote:
What's wrong with pymemcache, that we picked for tooz and are using for
2 years now?
https://github.com/pinterest/pymemcache
Looks like a good alternative.
--
Mehdi Abaakouk
mail: sil...@sileht.net
irc: sileht
On Fri, May 13 2016, Steve Martinelli wrote:
> /me gets the ball rolling
>
> Just when python3 support for keystone was looking like a reality, we've
> hit another snag. Apparently there are several issues with python-memcached
> in py3, putting it simply: it loads, but doesn't actually work.
On May 13, 2016 05:32, "Kiall Mac Innes" wrote:
>
> Hey Dims,
>
> From what I remember, oslo.cache seemed unnecessarily complex to use
> vs memcache's simplicity, and didn't have any usage docs[1] to help folks
> get started using it.
>
> I can see there is some docs under the
Hey Dims,
>From what I remember, oslo.cache seemed unnecessarily complex to use
vs memcache's simplicity, and didn't have any usage docs[1] to help folks
get started using it.
I can see there is some docs under the module index, but at a glance they
seem somewhat disconnected and incomplete.
On May 13, 2016 05:25, "Mehdi Abaakouk" wrote:
>>>
>>> - Is anyone interested in using pylibmc in their project instead of
>>> python-memcached?
>
>
> This is not a real drop-in replacement, pylibmc.Client is not threadsafe
> like python-memcached [1]. Aos it's written in C, it
- Is anyone interested in using pylibmc in their project instead of
python-memcached?
This is not a real drop-in replacement, pylibmc.Client is not threadsafe
like python-memcached [1]. Aos it's written in C, it shouldn't be a
problem for keystone because you don't use eventlet anymore, but for
On May 13, 2016 04:36, "Davanum Srinivas" wrote:
>
> Steve,
>
> Couple of points:
>
> * We can add pylibmc to g-r and phase out python-memcached over a time
period.
> * If folks are using python-memcached, we should switch then over to
> oslo.cache, then only oslo.cache will
Steve,
Couple of points:
* We can add pylibmc to g-r and phase out python-memcached over a time period.
* If folks are using python-memcached, we should switch then over to
oslo.cache, then only oslo.cache will reference either
python-memcached or pylibmc which will make the situation easier to
/me gets the ball rolling
Just when python3 support for keystone was looking like a reality, we've
hit another snag. Apparently there are several issues with python-memcached
in py3, putting it simply: it loads, but doesn't actually work. I've
included projects in the subject line that use
16 matches
Mail list logo