python / python/cpython

Normalize handling of negative timeouts in subprocess.py

Open
#90,946 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.10 3.11 3.8 (EOL) 3.9 (EOL) stdlib
Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Description

BPO 46790
Nosy @vstinner, @jkloth, @eryksun

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 2022-02-18.17:26:30.966>
labels = ['3.8', 'library', '3.9', '3.10', '3.11']
title = 'Normalize handling of negative timeouts in subprocess.py'
updated_at = <Date 2022-02-18.17:47:08.845>
user = 'https://github.com/jkloth'

bugs.python.org fields:

activity = <Date 2022-02-18.17:47:08.845>
actor = 'jkloth'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2022-02-18.17:26:30.966>
creator = 'jkloth'
dependencies = []
files = []
hgrepos = []
issue_num = 46790
keywords = []
message_count = 2.0
messages = ['413496', '413497']
nosy_count = 3.0
nosy_names = ['vstinner', 'jkloth', 'eryksun']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue46790'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10', 'Python 3.11']

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.

Research direction

Read subprocess.py first, focusing on the timeout-handling paths. Use the linked BPO issue and its discussion to determine the intended normalization for negative timeouts. Done means negative-timeout cases have consistent behavior across the affected subprocess operations.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.