execv (et al.) should invoke atexit handlers before executing new code

Open
#61,026 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

Start by reading the discussion linked as BPO issue 16822 and identify which execv-family functions and atexit behavior are in scope. The issue names no source files or tests, so locate the relevant implementation and tests from those entry points before assessing the change. Done means the specified handlers run before new code is executed.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 16822
Nosy @birkenfeld, @pitrou, @taleinat, @nedbat, @ericsnowcurrently, @emilyemorehouse

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 2012-12-30.22:38:28.866>
labels = ['type-feature']
title = 'execv (et al.) should invoke atexit handlers before executing new code'
updated_at = <Date 2018-07-08.07:15:25.829>
user = 'https://github.com/nedbat'

bugs.python.org fields:

activity = <Date 2018-07-08.07:15:25.829>
actor = 'taleinat'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2012-12-30.22:38:28.866>
creator = 'nedbat'
dependencies = []
files = []
hgrepos = []
issue_num = 16822
keywords = []
message_count = 8.0
messages = ['178623', '178668', '178669', '178670', '180337', '321155', '321167', '321264']
nosy_count = 7.0
nosy_names = ['georg.brandl', 'pitrou', 'taleinat', 'nedbat', 'neologix', 'eric.snow', 'emilyemorehouse']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue16822'
versions = ['Python 3.4']

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.