Issue 22 in pylibnidaqmx: enhancement: libraries probably shouldn't print to stdout
pylibn...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 22 by jpko...@gmail.com: enhancement: libraries probably
shouldn't print to stdout
http://code.google.com/p/pylibnidaqmx/issues/detail?id=22
Sometimes there are messages printed to STDOUT (e.g. when the library
generates a nidaqmx_h_x_x.py file). This interfered with an application I
made that expected specific strings printed to STDOUT. Obviously it was
not expecting the messages from pylibnidaqmx, and it was tricky to track
down, because pylibnidaqmx doesn't print very often. I think such output
belongs on STDERR instead, but I suppose it's a matter of opinion. Patch
attached.
Attachments:
stderr.patch 2.5 KB
pylibn...@googlecode.com
Status: Fixed
Comment #1 on issue 22 by pearu.peterson: enhancement: libraries probably
shouldn't print to stdout
http://code.google.com/p/pylibnidaqmx/issues/detail?id=22
Agreed.
Patch applied to svn repo.
Thanks!