Support contextvars in DelayedCall
Open
Nobody has claimed this yet.
core
enhancement
new
priority-normal
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@twm reported |
|---|---|
| Trac ID | trac#9824 |
| Type | enhancement |
| Created | 2020-05-11 07:44:16Z |
Capture the context when scheduling a call. Run the function in the context when its time comes.
Searchable metadata
trac-id__9824 9824
type__enhancement enhancement
reporter__twm twm
priority__normal normal
milestone__None None
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__None None
time__1589183056994430 1589183056994430
changetime__1589183056994430 1589183056994430
version__None None
owner__None None
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
Locate DelayedCall and the scheduling path in Twisted's core, then read the related issues #9807 and #9719 for context. Done means a scheduled call captures its context and runs the function in that context when due; verify the behavior with the relevant existing test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100