https://bugzilla.redhat.com/show_bug.cgi?id=2107901
Ben Beasley <code(a)musicinmybrain.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Link ID| |Github
| |snakemake/snakemake/issues/
| |1776
--- Comment #2 from Ben Beasley <code(a)musicinmybrain.net> ---
(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.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2107901