ResultsLog print statements from Python end up double-spaced

[Martyn Gigg]

From James Lord:

Python “print” statements in an Algorithm now come out double spaced in the Results Log window, with each argument on its own line, instead of all on one line as normal. Is this due to the move from the “Scripting Console” where print statements used to go? Scripts run “directly” in the Python Window still print normally in the lower pane.

[Martyn Gigg]

Append newline at QtSignalChannel level rather than MessageDisplay

The Poco log stream emits the log messages when it receives a newline but doesn't send along newlines. However, printing from Python scripts does produce newline characters so in order not to double-count them it makes most sense to simply emit a newline in the SignalChannel and let everything listening to it simply insert the exact text received.

Refs #7152

Changeset: 31426a07d78d7da2e2c673f927c247166837b6de

[Martyn Gigg]

Merge branch 'bugfix/7152_double_spaced_resultslog' into develop

[Martyn Gigg]

Branch: bugfix/7152_double_spaced_resultslog'

Tester: This algorithm below will help test this, copy it to the script window and execute to register it.

from mantid.api import *
from mantid.kernel import *

class HelloWorld(PythonAlgorithm):

    def PyInit(self):
        pass
        
    def PyExec(self):
        print 'Hello World'
#############################################################################################

AlgorithmFactory.subscribe(HelloWorld)

• Check that when starting MantidPlot the initial text comes out spaced with newlines as expected
• Register and run the algorithm and check that the text was printed as expected with only a single newline after the "Hello World" string
• Check that suppressing the newline in Python (add a comma to end of the "print 'Hello World'" line) now doesn't print one in the results log
• Run some algorithms to check that you get the expected output
• Run some interfaces, ConvertToEnergy (see http://www.mantidproject.org/Direct:ConvertToEnergy for instructions), for example and check the output is as expected.

[Karl Palmen]

Merge remote-tracking branch 'origin/bugfix/7152_double_spaced_resultslog' into master

[Martyn Gigg]

Append newline at QtSignalChannel level rather than MessageDisplay

The Poco log stream emits the log messages when it receives a newline but doesn't send along newlines. However, printing from Python scripts does produce newline characters so in order not to double-count them it makes most sense to simply emit a newline in the SignalChannel and let everything listening to it simply insert the exact text received.

Refs #7152

Changeset: eb7aad0f6ac1daafeeef12f7da497178574d2fe9

[Stuart Campbell]

This ticket has been transferred to github issue ​7998