Behavior of large returncodes (sys.exit(nn))

Open
#68,233 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the behavior of sys.exit(nn) with large values across the supported Python versions named in the issue. The payload names no source file or test, so locate the interpreter exit handling and its existing tests before defining the expected return-code behavior. Done means the behavior is documented by a regression test and the affected versions behave consistently.

Written by the indexing model from the issue text.

Description

3.11 3.12 3.13 interpreter-core type-bug
BPO 24045
Nosy @vadmium, @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 2015-04-24.00:47:08.979>
labels = ['type-bug', '3.8', '3.9', '3.10']
title = 'Behavior of large returncodes  (sys.exit(nn))'
updated_at = <Date 2021-02-26.19:37:05.463>
user = 'https://github.com/ethanfurman'

bugs.python.org fields:

activity = <Date 2021-02-26.19:37:05.463>
actor = 'eryksun'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2015-04-24.00:47:08.979>
creator = 'ethan.furman'
dependencies = []
files = []
hgrepos = []
issue_num = 24045
keywords = []
message_count = 4.0
messages = ['241903', '273846', '273851', '387740']
nosy_count = 4.0
nosy_names = ['Arfrever', 'docs@python', 'martin.panter', 'eryksun']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue24045'
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

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.