keyboard command leaves user hanging about oct2py HOT 4 CLOSED

That is tricky, I'll have to see if I can detect this condition. Otherwise, all I can do is document this shortcoming.

from oct2py.

I found a fix for this, I had to read characters instead of lines and look for the debug> prompt. I can recover the session, but I have to raise an Oct2PyError because the command does not complete successfully. Snippet:

           line = []
           while 1:
                char = self.proc.stdout.read(1).decode('utf-8')
                if char == '\n':
                    break
                elif char == '>' and ''.join(line) == 'debug':
                    self.proc.stdin.write('dbquit\n')
                    raise Oct2PyError('Debug point found, check for keyboard command:\n%s' % main_line)
                line.append(char)
            line = ''.join(line).strip()

I still need to update the test suite before finalizing, but I am out of gas the for now.

from oct2py.

Woohoo, now that I'm thinking clearly again, I was able to add full support for keyboard and debug points. A simple example:

from oct2py import octave as oc
oc.put('a', 1)
oc.keyboard()

A session might look like:

Entering Octave Debug Prompt...
debug> a
a = 1
debug> return
>>>

This resides in the dev branch for now. I will fix #32 and then push a new release.

from oct2py.

Very cool, thanks a lot!

from oct2py.