Make arg0 required argument in os.execl* functions
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- operating-systems
Research direction
Review the attached execl.diff and execlp.log first, then locate the os.execl* implementation and its tests in the current CPython tree. Confirm how the functions currently accept arguments and what existing coverage says; done means arg0 is required consistently across the os.execl* functions.
Written by the indexing model from the issue text.
Description
| BPO | 8191 |
|---|---|
| Nosy | @doko42, @bitdancer |
| Files |
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 2010-03-21.18:18:53.597>
labels = ['type-feature', 'library']
title = 'Make arg0 required argument in os.execl* functions'
updated_at = <Date 2014-02-03.17:11:37.818>
user = 'https://bugs.python.org/AlexanderBelopolsky'
bugs.python.org fields:
activity = <Date 2014-02-03.17:11:37.818>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2010-03-21.18:18:53.597>
creator = 'Alexander.Belopolsky'
dependencies = []
files = ['16613', '16980']
hgrepos = []
issue_num = 8191
keywords = ['patch']
message_count = 9.0
messages = ['101437', '101442', '101444', '103539', '103603', '103666', '103667', '190080', '190096']
nosy_count = 4.0
nosy_names = ['doko', 'Arfrever', 'r.david.murray', 'Alexander.Belopolsky']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue8191'
versions = ['Python 3.3']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100