on Wed Nov 12 2008, Alan Baljeu wrote:
>>This sounds perfectly reasonable to me, FWIW.
>>An interesting question then is how you embed your interactive Python shell
>>into the
> application's main event loop. But that's mainly an implementation detail. :-)
>>
>>Regards,
> > Stefan
>
> Well
>This sounds perfectly reasonable to me, FWIW.
>An interesting question then is how you embed your interactive Python shell
>into the application's main event loop. But that's mainly an implementation
>detail. :-)
>
>Regards,
> Stefan
Well, rendering is on a separate thread, so no issue the
Alan Baljeu wrote:
To solve this, I intend to write as much Python as possible, to drive
C++ objects, so I won't have to recompile, or restart my environment.
(Previous use of python had a slightly different goal: use Python
minimally for a dynamic modeling problem) So Python code will consist
>It seems your question is all about the boundary / interface between the (C++)
>application and the script that gets invoked: What should the content of the
>dictionary be, and what is the script expected to do with it ?
>In the most trivial case such a script could simply store named values
>(
Alan Baljeu wrote:
My question probably derives from ignorance of the Python way. I kind of
assumed people would advocate defining classes and methods, and then calling
those methods. You apparently see things otherwise.
Not really. I just see it as an orthogonal problem to the question you
y, November 11, 2008 4:25:00 PM
Subject: Re: [C++-sig] PyEval_EvalCode
Alan Baljeu wrote:
> I was reading some legacy code we have here, and discovered an unexpected
> idiom. Starting from C++, we create a dictionary, store a few named
> constants in there, and then call PyEval_Eva
Alan Baljeu wrote:
I was reading some legacy code we have here, and discovered an unexpected
idiom. Starting from C++, we create a dictionary, store a few named constants
in there, and then call PyEval_EvalCode passing in the dictionary. The code it
calls is a bunch of python files generated
I was reading some legacy code we have here, and discovered an unexpected
idiom. Starting from C++, we create a dictionary, store a few named constants
in there, and then call PyEval_EvalCode passing in the dictionary. The code it
calls is a bunch of python files generated from a CAD model, wi