make memoryview thread safe in free-threading
Open
Nobody has claimed this yet.
interpreter-core
topic-free-threading
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
memoryview is currently not safe against free-threading especially concurrent releasing the memoryviews. This issue track work to make it thread safe.
This is a follow-up to https://github.com/python/cpython/pull/127412#pullrequestreview-2472748568.
Linked PRs
- gh-154770
- gh-156248
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
Start with the follow-up pull request and the linked PRs gh-154770 and gh-156248 to understand the outstanding memoryview thread-safety work. Check how concurrent releasing is handled and verify that free-threading no longer permits unsafe concurrent releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100