in _win32ifaces.py, get the Windows error code when WSAIoctl and WSAAddressToString fail
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@exarkun reported |
|---|---|
| Trac ID | trac#5433 |
| Type | enhancement |
| Created | 2011-12-12 17:15:55Z |
win32GetLinkLocalIPv6Addresses makes two different calls using ctypes. When they fail, it doesn't check the error code to see what's going on or to make error reporting more informative. It would be better if it did. It's not totally obvious how to do this, since ctypes doesn't directly support retrieving the error information on all the versions of Python that Twisted supports (as of the filing of this ticket).
Searchable metadata
trac-id__5433 5433
type__enhancement enhancement
reporter__exarkun exarkun
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__tests tests
time__1323710155000000 1323710155000000
changetime__1323710155000000 1323710155000000
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 _win32ifaces.py at win32GetLinkLocalIPv6Addresses and inspect the ctypes calls to WSAIoctl and WSAAddressToString, along with the surrounding Windows-specific tests. Research how the supported Python versions expose Windows error information, then verify that failures report the relevant error code in the test suite.
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
- Mostly clear
- Newbie friendliness
- 38/100