Better handling of `anyhow::Error` and `eyre::Report`
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 1k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 66
Description
Both anyhow::Error and eyre::Report are for dynamic error handling, I think it's feasible to make some improvements:
- Unwrap inner error, if it's containing a
PyErr(However extra information should be combined to?) - Extract the error chain into an exception chain (since both libraries have
Error::chain/Report::chain)
I'm willing to contribute :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reviewing PyO3's existing PyErr conversion handling alongside the anyhow::Error and eyre::Report chain APIs; done means agreeing on how inner PyErr values and chained causes should map to Python exception chains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100