PyO3 / PyO3/pyo3

`no_std` support for `PyMutex`

Open
#6,436 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

PyMutex is a poisoning mutex. That means it has to check at runtime if the current thread is panicking. There is no way to do this in no_std. The current implementation of PyMutex cannot be supported without std.

I think we should add a non-poisoning variant, update the critical section API to accept either variant, and feature-gate the poisoning variant.

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

Start by locating the current PyMutex implementation and the critical section API. Read how poisoning and std dependencies are handled, then determine the changes needed for a non-poisoning variant and feature-gated poisoning support; done means the API supports no_std without requiring std.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.