LineReceiver and LineOnlyReceiver should work without a transport
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
 |
@itamarst reported |
|---|---|
| Trac ID | trac#5277 |
| Type | enhancement |
| Created | 2011-09-27 18:54:09Z |
While extremely useful in many cases, parsing lines is currently annoying as Line(Only)Receiver breaks if it doesn't have a transport. Both classes should support parsing lines without requiring a transport.
Searchable metadata
trac-id__5277 5277
type__enhancement enhancement
reporter__itamar itamar
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__
time__1317149649000000 1317149649000000
changetime__1317150775000000 1317150775000000
version__None None
owner__
cc__amacleod
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 locating the implementations of LineReceiver and LineOnlyReceiver and inspect where they assume a transport exists. Add tests covering line parsing without a transport, and consider the work complete when both classes parse lines successfully in that context without breaking transport-backed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100