unable to discover preferred HTTPConnection class

Open
#61,431 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
networking

Research direction

No source file or test is named; begin by locating the HTTPConnection classes in the Lib component and reviewing the Python 3.4 library behavior. The issue does not define how the preferred class should be discovered or specify a test, so confirm the expected discovery mechanism and acceptance criteria before starting.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 17229
Nosy @orsenthil

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 2013-02-18.21:21:11.778>
labels = ['type-feature', 'library']
title = 'unable to discover preferred HTTPConnection class'
updated_at = <Date 2015-02-13.17:54:39.431>
user = 'https://bugs.python.org/samwyse'

bugs.python.org fields:

activity = <Date 2015-02-13.17:54:39.431>
actor = 'demian.brecht'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-02-18.21:21:11.778>
creator = 'samwyse'
dependencies = []
files = []
hgrepos = []
issue_num = 17229
keywords = []
message_count = 1.0
messages = ['182343']
nosy_count = 2.0
nosy_names = ['orsenthil', 'samwyse']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17229'
versions = ['Python 3.4']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.