metwork-framework / cron-wrapper Goto Github PK

nose is not python 3.10 compliant
We should use nose2 or pytest

Hi @thefab, @Hawker65 and @thebaptiste,

thanks for conceiving this excellent program. I just found it indirectly through [1].

Extending my research, there is also

• cronwrap by @lowks, @imankulov and @desktable on behalf of @Doist
• croncoat by @MatthiasKauer with contributions from @lowks, @KeyMasterOfGozer and @imankulov
• Another cronwrap by @jonyesno written in Ruby
• lockrun by @SJFriedl written in Bash
• ... and probably more.

cronwrap and croncoat are already available on PyPI [2,3] and there is also another tool called cronwrapper [4]. However, the release package of cronwrapper available on PyPI apparently does not even include any code. After looking inside, I found it might have been conceived by Banio Carpenter (@baniobloom) and is currently maintained by @ranamalo, who also hosts its source code at [5].

However, all the Python implementations apparently didn't receive any commits within the last two years. I didn't investigate thoroughly if some features might be missing compared to the other tools, but I believe your variant to be pretty complete and advanced from my perspective.

So, it would be really nice to see your variant of cronwrapper to be published to PyPI in any way. However, as the name is already taken on PyPI, we might either ask @baniobloom or @ranamalo whether they want to carry on with their variant of cronwrapper or you might think about giving your variant a different name.

With kind regards,
Andreas.

[1] https://askubuntu.com/questions/179943/getting-notified-of-failed-cron-jobs
[2] https://pypi.org/project/cronwrap/
[3] https://pypi.org/project/croncoat/
[4] https://pypi.org/project/cronwrapper/
[5] https://github.com/ranamalo/cronwrapper

for example, after a reinstall, we can have a lock file owned by the old user which block the creation of a new lock (for the same command)