Message212988
func_name was not available on the places where the error strings are set (PyErr_Format), so I added it and passed it around as needed.
This is the simplest approach, but I am not sure it is the best (newbie here). Thus, I am waiting for your comments to improve the solution.
pjenvey noted I cannot just change PyEval_EvalCodeEx, since it is part of the interface. I intend to write a new function and call it from the old interface, setting func_name to co_name.
Before I do that, I want to check if this design is correct. Also, I am not sure what this new function would be called, I am not even sure what the "Ex" means in PyEval_EvalCodeEx. |
|
Date |
User |
Action |
Args |
2014-03-09 21:34:25 | mchelem | set | recipients:
+ mchelem, jcea, benjamin.peterson, erickt |
2014-03-09 21:34:25 | mchelem | set | messageid: <1394400865.44.0.405191749913.issue4322@psf.upfronthosting.co.za> |
2014-03-09 21:34:25 | mchelem | link | issue4322 messages |
2014-03-09 21:34:25 | mchelem | create | |
|