micropython / micropython/micropython
docs: explain optional global-interpreter-lock
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 22.1k
- Forks
- 9k
- Avg merge
- 6d 4h
- Merged PRs (30d)
- 16
Description
Documentation URL
Description
I saw this on the homepage:
multithreading via the "_thread" module, with an optional global-interpreter-lock (still work in progress, only available on selected ports)
My question:
So by default micropython does not have GIL? then does it use native multithreading instead of green thread? E.g on a Linux multicore machine?
And how to do mutex between different native threads?
Code of Conduct
Yes, I agree
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 homepage wording about _thread and the optional global-interpreter-lock. Check the documentation for selected ports and threading behavior, then clarify whether MicroPython uses native threads and how mutexes work. Done means the documentation answers the GIL, multicore, and mutex questions without ambiguity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100