castironpi <[EMAIL PROTECTED]> writes:
> On May 15, 6:26 am, [EMAIL PROTECTED] (R. Bernstein) wrote:
>> "Alan J. Salmoni" <[EMAIL PROTECTED]> writes:
>>
>> > I'm not sure if this is exactly what you're after, but try looking
>> > into the 'code' module.
>>
>> > It's fairly easy to make an interact
On May 15, 6:26 am, [EMAIL PROTECTED] (R. Bernstein) wrote:
> "Alan J. Salmoni" <[EMAIL PROTECTED]> writes:
>
> > I'm not sure if this is exactly what you're after, but try looking
> > into the 'code' module.
>
> > It's fairly easy to make an interactive interpreter that runs within
> > your progra
"Alan J. Salmoni" <[EMAIL PROTECTED]> writes:
> I'm not sure if this is exactly what you're after, but try looking
> into the 'code' module.
>
> It's fairly easy to make an interactive interpreter that runs within
> your program. If you import your programs variables into
> __main__.__dict__, you c
I'm not sure if this is exactly what you're after, but try looking
into the 'code' module.
It's fairly easy to make an interactive interpreter that runs within
your program. If you import your programs variables into
__main__.__dict__, you can have access to them which can be funky. You
can even o
The next release of pydb will have the ability to go into ipython from
inside the debugger. Sort of like how in ruby-debug you can go into
irb :-)
For ipython, this can be done pretty simply; there is an IPShellEmbed
method which returns something you can call. But how could one do the
same for th
