[Python-Dev] Capturing PyRun_String stdout

Amaury Forgeot d'Arc amauryfa at gmail.com
Tue Jun 30 22:48:44 CEST 2015


2015-06-30 21:40 GMT+02:00 Chris Moller <moller at mollerware.com>:

>  I expect this has been asked before, but I can't find out much about it...

Please ask this kind of questions on the python-users mailing list
<https://www.python.org/community/lists/> (or comp.lang.python).

There you will find helpful people who will tell you how to modify
sys.stdout, and the differences between exec() and eval().

Best of luck using Python!

> I'm trying to embed Python as a scripting language and I need to capture
> the output of PyRun_String(), PyEval_EvalCode(), or whatever as a char *
> (or wchar_t * or whatever) rather than have it go to stdout.
> Python 3.3.2 under plain C, not C++
> And, while I'm interrupting everyone's afternoon, another question: if I
> pass Py_single_input to PyRun_String() or
> Py_CompileString()/PyEval_EvalCode(), it accepts statements like "a=10" and
> can then properly do stuff like "print(a)".  If I use Py_eval_input
> instead, I get error messages.  In both cases, I'm using the same
> global_dict and local_dict, if that makes any difference.  What am I doing
> wrong?
> Thanks,
> Chris Moller
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/amauryfa%40gmail.com

Amaury Forgeot d'Arc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150630/6950b2ea/attachment.html>

More information about the Python-Dev mailing list