Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this project active? #36

Open
soumendrak opened this issue Aug 17, 2020 · 7 comments
Open

Is this project active? #36

soumendrak opened this issue Aug 17, 2020 · 7 comments

Comments

@soumendrak
Copy link

  • Anybody maintaining this project? As no PR accepted since 2016.
  • Any fork repo where latest PRs have been merged?
@fonsecajr
Copy link

fonsecajr commented Aug 18, 2020

Hi there.

There is a new project addressing the retry, https://github.com/jd/tenacity .

bye

@kbakk
Copy link

kbakk commented Sep 20, 2020

Wasn't aware of tenacity, will look into changing my code from using my fork of retry to this. Thanks!

@nilansaha
Copy link

nilansaha commented Jul 23, 2021

Tenacity does not have the same api structure as this one. Its a fork of retrying
I feel this library has so much better apis
I am thinking of making a fork of this one and tackling pending issues and PRs. Not sure how much support I will get

@benthorner
Copy link

I also prefer the succinct syntax of this library e.g. @retry(tries=7) (this library) is less typing than @retry(stop=stop_after_attempt(7)) (tenacity).

The library still works and is still useful (at least for me), but it could be even more useful if other people could contribute to it. I also found retry2, but that doesn't even allow issues.

@invl @rgreinho @williara any chance of adding other maintainers for the repo / package?

benthorner added a commit to benthorner/mock_serial that referenced this issue Nov 23, 2021
This isn't much better than having a custom retry function:

- The library isn't maintained [1], and the only other fork doesn't
accept issues [2].

- The default setting for the logger interferes with testing for
logger outputs.

- The syntax is still verbose (versus [3]) and a wrapper function
is still necessary.

On the whole it's good enough for now, and doesn't preclude having
a custom package in future if this one stops working.

[1]: invl/retry#36
[2]: https://github.com/eSAMTrade/retry
[3]: invl/retry#50
@rgreinho
Copy link
Contributor

I have nothing to do with this repo, except that I submitted one patch, so unfortunately I cannot help you @benthorner .

@leshchenko1979
Copy link

I have tried to push all major PRs from this project to this fork: https://github.com/leshchenko1979/reretry

If anyone wishes to participate, you are welcome!

@IllyaMoskvin
Copy link

For anyone who finds this topic via search, I recommend checking out backoff as an alternative:

https://pypi.org/project/backoff/

I'm not affiliated with that project. It just worked well for my needs, so it might work well for yours!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants