multiple issues in http.client

Open
#69,926 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading the original BPO issue 25740 and the http.client implementation to identify which separate problems the title refers to. Before changing anything, define a reproducible case and an explicit expected result for each issue; the work is done only when each case has been addressed and verified.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 25740
Nosy @vadmium, @spaceone

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 2015-11-27.00:35:22.170>
labels = ['type-bug', 'library']
title = 'multiple issues in http.client'
updated_at = <Date 2015-11-27.02:50:35.343>
user = 'https://github.com/spaceone'

bugs.python.org fields:

activity = <Date 2015-11-27.02:50:35.343>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-11-27.00:35:22.170>
creator = 'spaceone'
dependencies = []
files = []
hgrepos = []
issue_num = 25740
keywords = []
message_count = 3.0
messages = ['255445', '255449', '255450']
nosy_count = 2.0
nosy_names = ['martin.panter', 'spaceone']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25740'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5', 'Python 3.6']

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.