Implement search and domain for twisted.names.client
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
 |
@exarkun reported |
|---|---|
| Trac ID | trac#6090 |
| Type | enhancement |
| Created | 2012-10-10 13:02:09Z |
twisted.names.client.Resolver.parseConfig currently looks for these values in the resolv.conf contents given to it, but the results are never used.
See resolv.conf(5) for details on their meaning.
Searchable metadata
trac-id__6090 6090
type__enhancement enhancement
reporter__exarkun exarkun
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__names names
keywords__
time__1349874129000000 1349874129000000
changetime__1349874129000000 1349874129000000
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 in twisted.names.client.Resolver.parseConfig and inspect how it parses resolv.conf contents. Read resolv.conf(5) to understand the search and domain values, then trace where resolver configuration is consumed. Done means both parsed values affect name resolution as intended, with coverage for the resulting 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
- 45/100