Release the GIL around sendmsg and recvmsg
Open
Nobody has claimed this yet.
core
enhancement
new
priority-low
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@exarkun reported |
|---|---|
| Trac ID | trac#5643 |
| Type | enhancement |
| Created | 2012-04-12 21:23:42Z |
twisted.python.sendmsg.send1msg and twisted.python.sendmsg.recv1msg wrap potentially blocking I/O syscalls. The GIL should be released while the syscalls are running.
Searchable metadata
trac-id__5643 5643
type__enhancement enhancement
reporter__exarkun exarkun
priority__low low
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__
time__1334265822000000 1334265822000000
changetime__1334265881000000 1334265881000000
version__None None
owner__
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 locating twisted.python.sendmsg.send1msg and recv1msg and read how they wrap their potentially blocking I/O syscalls. Check the surrounding implementation and available tests, then verify that both syscalls run without holding Python's GIL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100