Make instrumentation pluggable

[hynek]

Ref #27

Does this look sufficient for you @jdunck (and everybody else)?

Rendered docs here: https://py-stamina--37.org.readthedocs.build/en/37/instrumentation.html

[jdunck]

Does this look sufficient for you @jdunck (and everybody else)?

I appreciate the work, will look at this soon, sorry for the delay.

[hynek]

Does this look sufficient for you @jdunck (and everybody else)?

I appreciate the work, will look at this soon, sorry for the delay.

Thanks! To be clear: I'm not asking for a code review – just whether it does everything you need. :)

[jdunck]

Looks good to me - tomorrow I'll try plugging it into datadog.

One small semantic question -

A hook is a callable, like a function, that takes a single argument: a stamina.instrumentation.RetryDetails object. Its return value is ignored.

It looks like if a hook raises, that will raise out of stamina. Is that intentional/desirable?

[hynek]

A hook is a callable, like a function, that takes a single argument: a stamina.instrumentation.RetryDetails object. Its return value is ignored.

It looks like if a hook raises, that will raise out of stamina. Is that intentional/desirable?

It is, because it's impossible to revert that user-side. You can always add a with suppress(): but vice versa is not possible. If there's need, we can even ship a @stamina.suppress_and_log_errors decorator or something I guess.

[hynek]

Looks good to me - tomorrow I'll try plugging it into datadog.

LMK when you need a third-party extensions wiki page. ;)