On Wed, Aug 21, 2013, at 12:42, David M. Welch wrote:
> Hi all,
>
> This is an old thread, but I'm having the same behavior in my terminal
> when
> I run some code but kill the process in the terminal (Ctrl-C). The code
> has
> two prime suspects (from a simple google search):
> 1. Creates ssh p
Hi all,
This is an old thread, but I'm having the same behavior in my terminal when
I run some code but kill the process in the terminal (Ctrl-C). The code has
two prime suspects (from a simple google search):
1. Creates ssh port forward via the subprocess module
(http://unix.stackexchange.com/q
In article ,
John O'Hagan wrote:
>On Mon, 19 Oct 2009, Aahz wrote:
>> In article ,
>> John O'Hagan wrote:
>>>
>>>I'm getting input for a program while it's running by using raw_input in a
>>>loop in separate thread. This works except for the inconvenience of not
>>> having a command history or t
On Mon, 19 Oct 2009, Aahz wrote:
> In article ,
>
> John O'Hagan wrote:
> >I'm getting input for a program while it's running by using raw_input in a
> >loop in separate thread. This works except for the inconvenience of not
> > having a command history or the use of backspace etc.
> >
> >That ca
In article ,
John O'Hagan wrote:
>
>I'm getting input for a program while it's running by using raw_input in a
>loop in separate thread. This works except for the inconvenience of not having
>a command history or the use of backspace etc.
>
>That can be solved by loading the readline module; ho
I'm getting input for a program while it's running by using raw_input in a
loop in separate thread. This works except for the inconvenience of not having
a command history or the use of backspace etc.
That can be solved by loading the readline module; however, it results in a
loss of visible a
