Howto on debugging Twisted applications
Open
Nobody has claimed this yet.
core
documentation
enhancement
new
priority-normal
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@itamarst reported |
|---|---|
| Trac ID | trac#5469 |
| Type | enhancement |
| Created | 2012-01-31 17:23:35Z |
There's the emacs appendix on debugging, but that's not quite sufficient or obvious.
Things to cover:
- Failure debug mode.
- Deferred debug mode.
- "Unhandled Deferred"'s gc dependency meaning errors might show up late
- trial/twistd -b.
- Encourage unit testing.
Searchable metadata
trac-id__5469 5469
type__enhancement enhancement
reporter__itamar itamar
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__documentation documentation
time__1328030615000000 1328030615000000
changetime__1328030615000000 1328030615000000
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 reviewing the existing Emacs debugging appendix and the documentation for failure debug mode, Deferred debug mode, unhandled Deferred errors, trial/twistd -b, and unit testing. The work is done when a clear how-to explains all five topics and makes the debugging workflow obvious to Twisted application developers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100