Bug 2107901
Summary: | Review Request: python-retry - Easy to use retry decorator | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ben Beasley <code> |
Component: | Package Review | Assignee: | Nobody's working on this, feel free to take it <nobody> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | package-review, sandhillsinvestment |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | Trivial | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-07-25 16:53:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1276941, 2039280 |
Description
Ben Beasley
2022-07-17 13:29:03 UTC
A fork of this at https://github.com/leshchenko1979/reretry has been updated for python3 (3.6, 3.7, 3.8, 3.9, 3.10) and is actively maintained. Last updated May 2022. I would suggest that the build for fedora be based on the fork and not on the unmaintained original. retry was last updated ~6 years ago. (In reply to Jeff from comment #1) > I would suggest that the build for fedora be based on the fork and not on > the unmaintained original. retry was last updated ~6 years ago. An interesting suggestion. I notice: - The fork has a new name, so it would be python-reretry. In theory both the original and the fork could be packaged. - Based on PyPI and GitHub statistics and Wheelodex reverse dependencies, the original is still much more popular (probably because it hasn’t yet broken on any of the new Python versions). I think the fork looks promising, although it isn’t entirely clear whether it will collect the momentum of the original user base or whether it will remain maintained after the initial burst of activity in May 2022. I’ve asked snakemake upstream if they would like to switch or not: https://github.com/snakemake/snakemake/issues/1776 Still, I think I’m going to go ahead and submit python-reretry for review, and write the small patch for snakemake to use it. I’m going to keep this open for a little while in case snakemake upstream points out some reason not to use reretry, but my expectation is that I will close this review as NOTABUG and patch snakemake to use reretry, which is up for review as bug 2110001. Closing this. It can be reopened if it turns out there is some overwhelming reason to use the original retry over the reretry fork. |