Py_CompileString and tracebacks

[badpenguin]

BPO	507477
Files	demo.c: a one-screen example showing the py_compilestring/py_evalcode bug

^{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 = <Date 2002-04-20.04:21:43.000>
created_at = <Date 2002-01-23.12:44:30.000>
labels = ['interpreter-core', 'invalid']
title = 'Py_CompileString and tracebacks'
updated_at = <Date 2002-04-20.04:21:43.000>
user = 'https://bugs.python.org/badpenguin'

bugs.python.org fields:

activity = <Date 2002-04-20.04:21:43.000>
actor = 'jhylton'
assignee = 'jhylton'
closed = True
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2002-01-23.12:44:30.000>
creator = 'badpenguin'
dependencies = []
files = ['308']
hgrepos = []
issue_num = 507477
keywords = []
message_count = 3.0
messages = ['8962', '8963', '8964']
nosy_count = 2.0
nosy_names = ['jhylton', 'badpenguin']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue507477'
versions = ['Python 2.2']

[badpenguin]

The API docs say, that when compiling a string with Py_Compilestring(code, filename, start), the filename param is used to construct the code object and may appear in tracebacks. Exceptions generated from these compiled objects evaluated with PyEval_EvalCode do not show this valuable description. This does not, somehow, apply when using Python's compile() and eval().

[jhylton]

Logged In: YES
user_id=31392

Can you explain in more detail what you think the bug is?
Or are there multiple bugs? From your description, it
sounds like something isn't right, but I can't tell exactly
what you'd like to see fixed. A small example would help.

[jhylton]

Logged In: YES
user_id=31392

Just noticed the attached program. PyRun_SimpleString() is
not the same as PyEval_EvalCode(), so they don't behave the
same. In particular, PyRun... has a call to
PyErr_Print(). If you check the return value of
PyEval_EvalCode() in your demo, you'll find that it is NULL,
which indicates an error. If you call PyErr_Print(), you'll
see the same traceback that PyRun... produces.