Exception context

[liamhuber]

Closes #59

I want to play around using it as a decorator, but I'm not yet convinced that the signature will be clean enough to be useful.

EDIT: I don't have time to play around with a decorator format. I'm not closed to it, I'd just rather leave it for later and already get access to what's here.

[github-actions]

👈 Launch a binder notebook on branch pyiron/pyiron_snippets/exception_context

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.34%. Comparing base (89a29c6) to head (88ea01e).
⚠️ Report is 20 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #60      +/-   ##
==========================================
+ Coverage   95.12%   95.34%   +0.22%     
==========================================
  Files          14       15       +1     
  Lines         574      602      +28     
==========================================
+ Hits          546      574      +28     
  Misses         28       28              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[pmrv]

Left a suggestion for docs, but otherwise looks good to me.

[pmrv]

Maybe a simple example that shows the use as a plain decorator would be nice, too.

>>> try:
...     with on_error(print, RuntimeError, 42):
...       raise RuntimeError()
... except RuntimeError:
...     pass
42

At least I expect to get the most mileage out of this incarnation.

[liamhuber]

Ah, absolutely. I had misunderstood how much power @contextlib.contextmanager was giving us -- I thought we additionally had to use it inside a regular exit stack.

I agree, many applications will need only a single callback, for which this is a much more condensed syntax 👍