Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #43185 > unrolled thread

standalone vs embedded interpreter

Back to article view | Back to comp.lang.python

Contents

  standalone vs embedded interpreter Nick Gnedin <ngnedin@gmail.com> - 2013-04-09 10:33 -0500
    Re: standalone vs embedded interpreter rusi <rustompmody@gmail.com> - 2013-04-09 08:52 -0700
      Re: standalone vs embedded interpreter Chris Angelico <rosuav@gmail.com> - 2013-04-10 02:14 +1000

#43185 — standalone vs embedded interpreter

Folks,

When simply I embed the interpreter:

	#include "Python.h"

	int main()
	{
	  Py_Initialize();
	  PyRun_InteractiveLoop(stdin,"test");
	  Py_Finalize();

	  return 0;
	}

I expect it to behave the same way as if I was running it as a 
standalone program. On Windows this is indeed the case, but on my Linux 
box (Python 3.3.1 (default, Apr  8 2013, 22:33:31) [GCC 4.1.2 20080704 
(Red Hat 4.1.2-51)]) I get a different behavior in handling console 
input. A standalone interpreter cycles though the input history when I 
use up and down arrows - say, I type this code:

 >>> 1
1
 >>> a=4
 >>> a
4

If I now press an <up> key in a standalone interpreter, I get 'a' placed 
at the prompt (my previous command). However, in an embedded code I get

 >>> ^[[A

put at the prompt - does anyone know what I am doing wrong?

Many thanks for any hint,

Nick

[toc] | [next] | [standalone]

#43188

On Apr 9, 8:33 pm, Nick Gnedin <ngne...@gmail.com> wrote:
> Folks,
>
> When simply I embed the interpreter:
>
>         #include "Python.h"
>
>         int main()
>         {
>           Py_Initialize();
>           PyRun_InteractiveLoop(stdin,"test");
>           Py_Finalize();
>
>           return 0;
>         }
>
> I expect it to behave the same way as if I was running it as a
> standalone program. On Windows this is indeed the case, but on my Linux
> box (Python 3.3.1 (default, Apr  8 2013, 22:33:31) [GCC 4.1.2 20080704
> (Red Hat 4.1.2-51)]) I get a different behavior in handling console
> input. A standalone interpreter cycles though the input history when I
> use up and down arrows - say, I type this code:
>
>  >>> 1
> 1
>  >>> a=4
>  >>> a
> 4
>
> If I now press an <up> key in a standalone interpreter, I get 'a' placed
> at the prompt (my previous command). However, in an embedded code I get
>
>  >>> ^[[A
>
> put at the prompt - does anyone know what I am doing wrong?
>
> Many thanks for any hint,
>
> Nick

You probably need readline
See http://docs.python.org/2/library/cmd.html#cmd.Cmd.cmdloop
[Also try Control-P COntrol-N for up and down arrow]

[toc] | [prev] | [next] | [standalone]

#43193

On Wed, Apr 10, 2013 at 1:52 AM, rusi <rustompmody@gmail.com> wrote:
> You probably need readline
> See http://docs.python.org/2/library/cmd.html#cmd.Cmd.cmdloop
> [Also try Control-P COntrol-N for up and down arrow]

Be aware that GNU readline is GPL, not LGPL. This may have
consequences if you distribute your code.

ChrisA

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web