On 8/8/2011 11:17 AM, Francis Labarre wrote:
Hello everyone,
I'm currentlytrying to port some embedded code from python 2.7 to python
3.2.
The current code replicate the basic behavior of the python interpreter
in an
MFC application. When a command is entered in our embedded interpreter,
we wri
ughthe api.
I'll look into it, thank again.
F.L.
> Date: Mon, 8 Aug 2011 19:52:14 +0200
> From: t...@jollybox.de
> To: python-list@python.org
> Subject: Re: Embedded python console and FILE* in python 3.2
>
> On 08/08/11 19:44, Thomas Jollans wrote:
>
> >
> > 1
On 08/08/11 19:44, Thomas Jollans wrote:
> If you use the same workflow as you do currently, it won't:
>
> 1. Feed input to your custom stdin object, which will buffer the code.
> 2. Call PyRun_IteractiveOne - it will read from your object, which will
>return the buffer contents.
> 3. The resu
On 08/08/11 19:14, F L wrote:
>> Is the `code` module (http://docs.python.org/library/code.html) an
> insufficiently exact copy of an interpreter for you?
>
> The problem isn't really to emulate the behavior of the interpreter as
> to obtain the result of the execution as a string in c++.
> The c
> Is the `code` module (http://docs.python.org/library/code.html) an
> insufficiently exact copy of an interpreter for you?
The problem isn't really to emulate the behavior of the interpreter as to
obtain the result of the execution as a string in c++. The code module doesn't
seem to help with
Is the `code` module (http://docs.python.org/library/code.html) an
insufficiently exact copy of an interpreter for you?
On Mon, Aug 8, 2011 at 4:17 PM, Francis Labarre
wrote:
> Hello everyone,
>
> I'm currently trying to port some embedded code from python 2.7 to python
> 3.2.
>
> The current co
On 08/08/11 17:17, Francis Labarre wrote:
> Hello everyone,
>
> I'm currently trying to port some embedded code from python 2.7 to
> python 3.2.
>
> The current code replicate the basic behavior of the python interpreter
> in an
> MFC application. When a command is entered in our embedded interpr
