spawnProcess-based WSGI container
Open
Nobody has claimed this yet.
enhancement
new
priority-normal
web
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@glyph reported |
|---|---|
| Trac ID | trac#5180 |
| Type | enhancement |
| Created | 2011-07-06 23:34:53Z |
We should have a WSGI container that supports using processes instead of threads, for utilizing multiple cores. The 'twistd web' command line should allow for use of this as well.
Searchable metadata
trac-id__5180 5180
type__enhancement enhancement
reporter__glyph glyph
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__web web
keywords__
time__1309995293000000 1309995293000000
changetime__1560836552382607 1560836552382607
version__None None
owner__None None
cc__jknight cc__Julian
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 existing WSGI container and the twistd web command-line entry point. Determine how the current container manages execution and where the command selects it. Done means a process-based WSGI option is available through twistd web and uses multiple processes for core utilization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100