Logging output should be copied to the manhole client
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#101 |
| Type | enhancement |
| Created | 2003-07-18 06:43:32Z |
Searchable metadata
trac-id__101 101
type__enhancement enhancement
reporter__exarkun exarkun
priority__low low
milestone__
branch__
branch_author__
status__new new
resolution__
component__core core
keywords__
time__1058510612000000 1058510612000000
changetime__1264692259000000 1264692259000000
version__
owner__acapnotic acapnotic
cc__exarkun cc__acapnotic
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
No files, tests, or entry points are named. Start by locating Twisted's logging and manhole components, then determine how logging output is currently delivered and what the manhole client should receive. Done means the requested logging output is copied to the manhole client with behavior covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 15/100