Accepted suggestions from cargo fmt and cargo clippy to fix the CI errors related to rustfmt and clippy.

• All existing tests passed

Regarding the macOS-latest CI failure, I believe updating the pyo3 crate to a more recent version that supports Python 3.13 might resolve the issue.

Since version 22.0, pyo3 seems to be adding support for Python 3.13.
However, I consider upgrading package versions a critical decision that shouldn't be made alone.

My proposal is to update the eyre Cargo.toml as follows:

[dependencies]
...
pyo3 = { version = "0.23.1", optional = true, default-features = false }
...

[dev-dependencies]
...
pyo3 = { version = "0.23.1", default-features = false, features = ["auto-initialize"] }

@yaahc, would this be a valid approach? I'm open to any suggestions or feedback.

tenatively that sounds fine, the only concern would be whats the MSRV for that version of pyo3 since we'd inherit it

Looking at the release history of the pyo3 crate, the current version being used (0.20) has a MSRV of 1.56.0. Starting from version 0.22.0, the MSRV was raised to 1.63.0.
Is it okay if I proceed with the change?

• crate.io version history
• Release 0.22.0 Notes