the test suite should honor an http_proxy for running the test suite

Open
#61,984 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
networking, testing

Research direction

Start by reviewing the Python test suite's handling of network-related tests and environment variables, then determine where an http_proxy should be honored. The work is done when the relevant tests use the configured proxy and the suite's behavior is covered by tests; no specific files are named in the issue.

Written by the indexing model from the issue text.

Description

tests type-feature
BPO 17784
Nosy @doko42, @raulcd

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-04-17.21:44:44.815>
labels = ['type-feature', 'tests']
title = 'the test suite should honor an http_proxy for running the test suite'
updated_at = <Date 2019-03-15.22:09:02.180>
user = 'https://github.com/doko42'

bugs.python.org fields:

activity = <Date 2019-03-15.22:09:02.180>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2013-04-17.21:44:44.815>
creator = 'doko'
dependencies = []
files = []
hgrepos = []
issue_num = 17784
keywords = []
message_count = 2.0
messages = ['187208', '228124']
nosy_count = 2.0
nosy_names = ['doko', 'raulcd']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17784'
versions = ['Python 3.5']

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.