Re: [jupyter] interact with command-line tools from the notebook

2017-06-12 Thread Lawrence D’Oliveiro
On Monday, June 12, 2017 at 11:27:08 PM UTC+12, takowl wrote: > > On 10 June 2017 at 00:12, Lawrence D’Oliveiro > wrote: > >> Isn’t that what select >> is for? > > > select() will tell you whether there's space in a buffer

Re: [jupyter] interact with command-line tools from the notebook

2017-06-12 Thread Thomas Kluyver
On 10 June 2017 at 00:12, Lawrence D’Oliveiro wrote: > Isn’t that what select is > for? select() will tell you whether there's space in a buffer to write to for a given fd. But you can write to the master side of a pty

Re: [jupyter] interact with command-line tools from the notebook

2017-06-09 Thread Lawrence D’Oliveiro
On Wednesday, May 17, 2017 at 3:50:33 AM UTC+12, takowl wrote: > > There's nothing automatic, because we can't tell when a process is waiting > for input. > Isn’t that what select is for? -- You received this message because you are subscribed

Re: [jupyter] interact with command-line tools from the notebook

2017-05-16 Thread Denis Akhiyarov
Ok, I understood that this is difficult after trying out 2 options :) pexpect support on Windows is partial and experimental, hence I will not even try this. Anyway working with command-line tools right from ipython/jupyter would be very handy, especially for presentations! On Tue, May 16, 2017

Re: [jupyter] interact with command-line tools from the notebook

2017-05-16 Thread Thomas Kluyver
There's nothing automatic, because we can't tell when a process is waiting for input. If you know what the prompt looks like, you may be able to use something like pexpect.replwrap to run it - though I don't know if that will work on Windows. On 16 May 2017 at 13:22, Denis Akhiyarov

[jupyter] interact with command-line tools from the notebook

2017-05-16 Thread Denis Akhiyarov
Is there any way I can interact with command-line tools from the notebook? For example scriptcs embeds itself in cmd as a REPL. In the notebook it is not interactive. In fact I cannot even kill the scriptcs process () when it is called in the notebook: taskkill /f /im scriptcs* ERROR: The