Re: [openstack-dev] [oslo][oslo.service] looping.RetryDecorator behavior

Ok, thanks Josh. We switched to tenacity and it works very well for us ) Renat Akhmerov @Nokia On 23 Sep 2017, 11:51 +0700, Joshua Harlow , wrote: > Hi Renat, > > I was more just saying that depending on your situation it might be > better to switch to using tenacity (not

Re: [openstack-dev] [oslo][oslo.service] looping.RetryDecorator behavior

Hi Renat, I was more just saying that depending on your situation it might be better to switch to using tenacity (not that the retry decorator is deprecated, though I wouldn't personally use it). As you mentioned in https://bugs.launchpad.net/oslo.service/+bug/1718635/comments/1 this class

Re: [openstack-dev] [oslo][oslo.service] looping.RetryDecorator behavior

Thanks Josh, I’m not sure I fully understand your point though. You mean it’s a legacy (deprecated?) code that we should never use in our code? Should it be considered a private class of oslo_service? In our global requirements tenacity is configured as "tenacity>=3.2.1”, should we bump it to

Re: [openstack-dev] [oslo][oslo.service] looping.RetryDecorator behavior

It does look like is sort of a bug, Though in all honesty I wouldn't be using oslo.service or that looping code in the future for doing retrying... https://pypi.python.org/pypi/tenacity is a much better library with more `natural` syntax and works more as one would expect (even under