Check comments about RFC-compliance issues
Open
Nobody has claimed this yet.
enhancement
names
new
priority-normal
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@evilham reported |
|---|---|
| Trac ID | trac#9552 |
| Type | enhancement |
| Created | 2018-10-15 20:17:41Z |
Code contains comments about RFC compliance issues.
This should be investigated.
Searchable metadata
trac-id__9552 9552
type__enhancement enhancement
reporter__evilham evilham
priority__normal normal
milestone__None None
branch__
branch_author__
status__new new
resolution__None None
component__names names
keywords__None None
time__1539634661540605 1539634661540605
changetime__1539634661540605 1539634661540605
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
Search the Twisted codebase for comments that mention RFC compliance and inspect each comment in the context of the surrounding implementation. Compare the stated concerns with the relevant RFC requirements, then document or address the identified compliance issues and verify the affected behavior with the existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100