PyO3 / PyO3/pyo3

Custom Error types for `FromPyObject`

Open
#5,391 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
16.2k
Forks
1k
Avg merge
2d 6h
Merged PRs (30d)
66

Description

Some FromPyObject impls can make use of more specialized error types:

  • set extraction it looks like the error is essentially a downcast error or the key extraction error

  • PyRef/PyClassGuard is a downcast error or borrow error
  • ...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The entry points are the FromPyObject implementations, especially set extraction and PyRef/PyClassGuard. Start by reviewing their existing error paths and determine which cases correspond to downcast, borrow, or key-extraction errors. Done means the relevant implementations use the appropriate specialized error types.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
api, backend-api-design
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.