Matlab is the native language of the group for which I am building this
interface. It is for access to ocean sensor data, and it's being done this
way so the scientists whose sensors they are can use a significant body of
legacy code in their analyses. (Though I was planning to sneak in an option
to use python scripts because that's what I prefer.)
But the fact remains that I have no trouble capturing stdout when I run
this python on the command line and it doesn't work when I run it as part
of a Django views.py and I don't where to begin trying to understand why
not.
-Tom
On Fri, Dec 4, 2020 at 3:33 PM Kris A. Stern <krisast...@gmail.com> wrote:
> Why not try something Python based instead which is also free. What kind
> of functionality are you looking for? Are you planning to plot, if so you
> could try numpy, scipy, and matplotlib.
>
> On Sat, 5 Dec 2020 at 02:02, Tom Sgouros <tsgou...@gmail.com> wrote:
>
>> Anybody have any random thoughts about this? I have run out of ideas to
>> test.
>>
>> Thank you,
>>
>> -Tom
>>
>> On Wed, Dec 2, 2020 at 10:32 PM Tom Sgouros <tsgou...@gmail.com> wrote:
>>
>>> Hello all:
>>>
>>> I have a Django application that dispatches processing to a matlab
>>> script using exec. How can I capture the stdout and stderr of the script's
>>> execution?
>>>
>>> Outside of Django, this works for a dumb matlab script called tt that
>>> just prints a message:
>>>
>>> >>> import matlab.engine, StringIO
>>> >>> eng = matlab.engine.start_matlab()
>>> >>> out = StringIO.StringIO()
>>> >>> err = StringIO.StringIO()
>>> >>> exec('eng.tt(25, stdout=out, stderr=err)')
>>> >>> out.getvalue()
>>> "This is a disp command.\n\nret =\n\n '25\n\n"
>>>
>>> Inside a Django method, the exec seems to function properly, but the out
>>> and err variables remain empty. Where's my output? Did the logging system
>>> snatch it? I assume I'm missing something obvious here but any pointers
>>> would be welcome.
>>>
>>> Thank you,
>>>
>>> -Tom
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to django-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/35b264b3-f793-4131-a6e4-700e51aebbfan%40googlegroups.com
>>> <https://groups.google.com/d/msgid/django-users/35b264b3-f793-4131-a6e4-700e51aebbfan%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/CAFUviqs6XXxfzOqQ4uCnVBEo2cN%2BbMMPHPEO-wtbxPVa94PtHw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/django-users/CAFUviqs6XXxfzOqQ4uCnVBEo2cN%2BbMMPHPEO-wtbxPVa94PtHw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAMxZ8Sm7avV%3Df664b%3D8hYQWgAUwvpL%2BLVZV%3D31Hy21B2xeSDtA%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-users/CAMxZ8Sm7avV%3Df664b%3D8hYQWgAUwvpL%2BLVZV%3D31Hy21B2xeSDtA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/CAFUviqvvOZUorVSmT1DSe_GO53_UEntvshiEzLxtUCAg%2BRFcPw%40mail.gmail.com.
