Provide a fake version of IReactorThreads and a ThreadPool that runs synchronously.
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
 |
@tomprince reported |
|---|---|
| Trac ID | trac#8295 |
| Type | enhancement |
| Created | 2016-04-15 21:32:14Z |
When testing code that uses threads, one often doesn't actually care if the code is run asynchronously. Particularly if SynchronousTestCase and the synchronous deferred helpers are being used, it is preferable if the code is not run asynchronously.
Attachments:
- NonThreadThings.py (924 bytes) - added by exarkun on 2016-04-16 11:50:22Z -
Searchable metadata
trac-id__8295 8295
type__enhancement enhancement
reporter__tom_prince tom.prince
priority__normal normal
milestone__None None
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__None None
time__1460755934992869 1460755934992869
changetime__1460807970116423 1460807970116423
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
Start by reading the attached NonThreadThings.py and locating the IReactorThreads and ThreadPool entry points in the Twisted core. Review existing thread-related tests and determine the expected synchronous behavior; done means test code can use fake thread APIs without asynchronous execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100