test_support.find_unused_port can cause socket conflicts on Windows
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- operating-systems, testing-qa
Research direction
Start by reading the test_support.find_unused_port implementation and the historical unused1.patch and test_logging.patch linked in the issue. Reproduce the socket-conflict behavior on Windows, then use the existing tests and Windows test configuration to verify that find_unused_port no longer causes conflicts.
Written by the indexing model from the issue text.
Description
| BPO | 8576 |
|---|---|
| Nosy | @pitrou, @giampaolo, @tjguk, @tpn, @bitdancer, @iritkatriel |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2010-04-30.09:18:02.537>
labels = ['type-bug', '3.8', '3.9', '3.10', 'tests', 'OS-windows']
title = 'test_support.find_unused_port can cause socket conflicts on Windows'
updated_at = <Date 2020-11-06.18:15:25.893>
user = 'https://github.com/pfmoore'
bugs.python.org fields:
activity = <Date 2020-11-06.18:15:25.893>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests', 'Windows']
creation = <Date 2010-04-30.09:18:02.537>
creator = 'paul.moore'
dependencies = []
files = ['17150', '17161']
hgrepos = []
issue_num = 8576
keywords = ['patch', 'buildbot']
message_count = 23.0
messages = ['104614', '104638', '104651', '104677', '104701', '104710', '104715', '104724', '104806', '104807', '104822', '104843', '104845', '104891', '104893', '104951', '104952', '104954', '104955', '219947', '219950', '236969', '380463']
nosy_count = 7.0
nosy_names = ['exarkun', 'pitrou', 'giampaolo.rodola', 'tim.golden', 'trent', 'r.david.murray', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue8576'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100