is this awsretry or gd-awsretry?

[tbradley-sans]

This project seems to have a small identity crisis. https://pypi.org/project/gd-awsretry/ says the way to install it is pip install gd-awsretry. But https://github.com/linuxdynasty/awsretry says to install it by pip install awsretry. Which is right?

[linuxdynasty]

Looks like someone copied it?

[tbradley-sans]

Yeah, I guess. The whole thing seems kinda fishy.

[nmerket]

I've been down too much of a rabbit hole with this one. It looks like gd-awsretry is a fork of this repo. A little sleuthing on pypi and github seems to have revealed that @dwabece is the guy behind gd-awsretry, but I can't seem to find the repo. The last time awsretry was updated was May 2017 and gd-awsretry was updated in May 2019. So now I'm in a quandry, do I use awsretry even though it looks like it hasn't had a lot of love recently, or do I try this mysterious fork gd-awsretry that has some more recent work? I'm leaning towards using the OG because I can't find the repo for the fork and that's a pretty big red flag in my mind.

[linuxdynasty]

Question is something wrong with the current awsretry? I haven't updated pypi in a while. I can do that over the weekend.

[tbradley-sans]

@nmerket I just gave up and rolled my own.

Question is something wrong with the current awsretry?

What do you even mean by "current awsretry"? The one that hasn't been touched in over 2 years?

What's wrong with it is that nobody trusts an open source library that has been abandoned by its maintainers.

[nmerket]

I tried the old awsretry and it seems to work fine. I share my concern with @tbradley-sans that I'm leery to write code that depends on a library that isn't being maintained. If there are updates, yes, that would be awesome if you pushed them to pypi.

[linuxdynasty]

@nmerket I will push the updates I have. It's not many as the module has work for the intended purpose.