Pickle Support
Open
Nobody has claimed this yet.
needs-design
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 1k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 66
Description
As of right now its not possible to pickle classes created by PyO3.
This feature would be invaluable for situations where some form of persistence would be desireable.
As of right now it has trouble pickling after I call
#[new]
fn __new__(obj: &PyRawObject) -> PyResult<()>{
Otherwise the .__dict__ attributes are maintained prior to initialization with __new__
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
The report concerns PyO3 classes using a Rust #[new] constructor and their Python dict; no source file or test is named. Start by reproducing the pickle failure around that constructor, then define and verify behavior for pickling and restoring the class state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100