Add retrying shim

Introduces a shim that should enable drop-in replacement for the unmaintained https://github.com/rholder/retrying project.

Path towards fix for: https://github.com/jd/tenacity/issues/356

An alternative approach might be to claim the name on PyPI and then publish a dummy package (with a breaking version number) with the shim. Over time you could standardise on one name or the other and log warnings and eventually fail (with another breaking version number).

⚠️ No release notes detected. Please make sure to use reno to add a changelog entry.

Not sure this fixes/help with anything though?

Yes, agree. Was thinking that it might assist individuals migrating to tenacity without changing imports, but it probably isn’t necessarily the best strategy.

Taking a step back, what would you like to see happen with “retrying” on pypi. It’s presently abandoned so is a supply chain risk / unmaintained code.

If you want the pypi project name, you should submit a 541 request because they take 2 or 3 months to process. https://github.com/pypa/pypi-support/issues/2064#issuecomment-1194395022

Some ideas for how to migrate pypi packages.

Option 1: Over time, migrate tenacity users to retrying

Option 2: Over time, migrate retrying users to tenacity

Option 3: Keep users of both packages as-is, but without maintaining 2 packages and code bases long-term (I’m not sure this is possible or desirable)

⚠️ No release notes detected. Please make sure to use reno to add a changelog entry.