PyO3 / PyO3/pyo3

Support `__del__`

Open
#2,479 2 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

I'd like to be able to use a __del__ method in #[pymethods], however it's not being called.

There are two other related issue #402 and #774. #774 seems most relevant but the OP get's told they shouldn't be using __del__. AFAIK issuing a ResourceWarning is a legitimate use of __del__.

I could print a warning in Drop but that won't be a python warning and will confuse people, without support for __del__ I don't see another way around this.

Related PR https://github.com/samuelcolvin/watchfiles/pull/164

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

Review how #[pymethods] currently handles object lifecycle methods, comparing the requested del behavior with Rust Drop and Python ResourceWarning semantics. Read related issues #402 and #774 first; done means defining and validating supported del behavior without relying on a Rust-only warning.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.