-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stdout is delayed? #45
Comments
Interesting. I have looked at this a bit, but I can't find the problem. It seems that Matlab buffers some of its outputs, and only prints them to stdout on the next |
Thanks for looking into it. Strangely it only happens sporadically. |
I'll keep this open in case I stumble across a solution |
First, good job. It is working much better than the engine provided by Matlab . I am running Python 3.6 with Matlab 2018b and I just don't have any stdout at all. I post this here because I am pretty sure it is related. I tried playing with your start reader function but nothing worked.
I tried the following and I am "getting in of thread" and never getting print('getting out of thread') and never 'getting line'
So I guess that stdout.readline is never returning anything. Hope it helps |
I'm assuming you are running Windows? Matlab simply does not write to stdout on Windows (as is noted in the README). Which is just sad, but there's nothing to be done about it as far as I know. If you need to capture output, you can always make your function calls with |
When I run the following command the STDOUT from Matlab is not transferred:
Strangely, I get the output later after running a few more commands.
The text was updated successfully, but these errors were encountered: