PyO3 / PyO3/pyo3

Expand performance section of the guide

Open
#3,310 9 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

  • Overhead of conversions (i.e. PyList vs Vec etc.)
  • String intern!
  • Vec<u8> becoming list[int] (and thus being very slow), usage of Cow<[u8]> as an alternative
  • #[pyo3(get)] deep-cloning non-Py data
  • dictionary dispatch, i.e. look-up based on type object identity

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

Locate the guide's existing performance section and read the surrounding conversion and attribute documentation for PyList, Vec, String, Cow, and #[pyo3(get)]. Cover each unchecked topic in the issue, including conversion overhead, interning, Vec behavior, deep cloning, and dictionary dispatch, so the performance guidance is complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
documentation, performance
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.