cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Discussions

Solve problems, and share tips and tricks with other JMP users.
Choose Language Hide Translation Bar
AlterEgo
Level III

Bug: Python print() to JMP Log ignores whitespace-only arguments

When using the Python console with output directed to the JMP Log, print() does not behave consistently with standard Python. Arguments consisting only of whitespace characters (spaces, tabs, newlines, etc.) appear to be discarded rather than printed. For example:
print('a', 'b')   # Output: ab; even the space as the default separator is ignored
print('a', 'b', sep=' ')   # Output: ab
print('a', '     ', 'b')   # Output: ab
print('a', 'b', sep='    ')   # Output: ab
print('a', '\t', 'b')      # Output: ab
print('a', '\n', 'b')      # Output: ab
print('a', '\r\n', 'b')    # Output: ab​
On the other hand, breaks work correctly when embedded within a string, e.g.:
print('a\nb')
 
(Widows 11, JMP 19.0.1)
3 REPLIES 3
jthi
Super User

Re: Bug: Python print() to JMP Log ignores whitespace-only arguments

JMP19.1.5

jthi_0-1790848989988.png

 

-Jarmo
AlterEgo
Level III

Re: Bug: Python print() to JMP Log ignores whitespace-only arguments

I guess I can wait for a new version, then check again.

AlterEgo_0-1790935877476.png

Edit:

Funny, in Scripting Index example window it works ok:

AlterEgo_0-1790936552829.png

 

Re: Bug: Python print() to JMP Log ignores whitespace-only arguments

I am assuming this the Global Log window vs an Embedded Log window in the script editor?  It appears to work fine when the output goes to the Embedded Log, but even with 19.2  global 'log' window is trimming out white space.  If the Embedded Log output isn't sufficient, please contact Tech Support and file a bug report.

Recommended Articles