New module: doc versus action

[terryjreedy]

BPO	951482
Nosy	@rhettinger, @terryjreedy

^{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 = 'https://github.com/rhettinger'
closed_at = <Date 2004-08-17.02:32:25.000>
created_at = <Date 2004-05-10.20:01:52.000>
labels = ['library']
title = 'New module: doc versus action'
updated_at = <Date 2004-08-17.02:32:25.000>
user = 'https://github.com/terryjreedy'

bugs.python.org fields:

activity = <Date 2004-08-17.02:32:25.000>
actor = 'rhettinger'
assignee = 'rhettinger'
closed = True
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2004-05-10.20:01:52.000>
creator = 'terry.reedy'
dependencies = []
files = []
hgrepos = []
issue_num = 951482
keywords = []
message_count = 2.0
messages = ['20757', '20758']
nosy_count = 2.0
nosy_names = ['rhettinger', 'terry.reedy']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue951482'
versions = []

[terryjreedy]

Because the functions in the new module give direct
access to API functions, syntactically legal code that
uses them can be more fragile than normal -- leading to
possible core dumps (which are normally considered to
be interpreter bugs).

Should Lib Ref 3.27 warn about this possibility?
Can the interfacing be strengthened to cover at least
some bad inputs?
Can ceval be strengthed without slowing it down?

[rhettinger]

Logged In: YES
user_id=80475

Michael Hudson patched compile.c to make PyNew_Code less
susceptible to bogus arguments. See Python/compile.c 2.315

Also, I expanded the warnings in the docs for the new
module. See Doc/lib/libnew.tex 1.10.