mattrobenolt / mattrobenolt/alloconda
GIL release ergonomics
Open
Nobody has claimed this yet.
core
- Dominant language
- Zig
- Stars
- 7
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Add support for releasing the GIL during CPU-bound Zig work.
// Desired pattern (Zig-friendly, no closures):
var state = gil.release();
defer state.acquire();
// ... CPU-bound work with GIL released ...
Open questions:
- Research pyo3's default GIL behavior - do they auto-release?
- Determine interaction with free-threaded Python (PEP 703)
- Decide on default: hold GIL vs release GIL per-function
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 by researching pyo3's default GIL behavior and the interaction with free-threaded Python under PEP 703. Use the desired Zig-friendly release/acquire pattern as the API goal, then resolve whether functions hold or release the GIL by default. Done means the supported behavior and default policy are specified clearly enough to implement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, zig
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100