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().
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.
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.
