Fortran code wrapped with f2py doesn't have its output redirected correctly

[Martyn Gigg]

f2py is contained within numpy and allows a python interface to be generated for Fortran code.

Currently any Fortran routines that contain print statements do not function as expected in MantidPlot. The print output only ever gets seen on the command line and not where it would be expected in the scripting window.

Attached are the necessary windows files for f2py, gfortran and mingw along with a test module containing a hello() function from Steve King.

[Martyn Gigg]

File are actually to big so I'll keep them for now.

[Martyn Gigg]

There is also a problem with error translation in MantidPlot. If the fortran function has an error, i.e. cannot open a file, and f2py tries to raise an Exception then this kills MantidPlot.

[Nick Draper]

Bulk move of tickets to iteration 27, if your ticket is essential for Iteration 26 then move it back.

[Martyn Gigg]

Further investigation has revealed that there is no ideal way to solve this.

The issue is that the Fortran routines write directly to the stdout file descriptor, which bypasses the Python stdout object. Our GUI and IDLE both pick up their standard output from the Python object.

One way is to capture all stdout to a file instead, as the fortran stdout can be captured this way and then output that in one go. It's not ideal though as this would have to be lagged behind the execution. We could consider threading a function that simply checks if stdout as been written and reads this as it goes along?

On the error translation side, I think this is going to be even more hopeless. It seems that f2py doesn't translate it's errors into Python exceptions as standard, this means that it has to be done by the person who writes the code which is less than ideal.

[Nick Draper]

Bulk move of tickets at the end of iteration 27

[Nick Draper]

Bulk move of tickets at the end of iteration 28

[Nick Draper]

Accepted and assigned tickets moved at iteration 29 code freeze

[Nick Draper]

Bulk move of tickets to iteration 31 at the iteration 30 code freeze

[Nick Draper]

Moved to iteration 33 at iteration 32 code freeze

[Nick Draper]

Moved at end of release 2.1

[Nick Draper]

http://www.mantidproject.org/Release_Notes_2_2_Full_List

[Nick Draper]

Moved to release 2.4

[Nick Draper]

Moved to r2.6 at the end of r2.5

[Martyn Gigg]

I don't think there is anything that can be done here.

[Russell Taylor]

Fine by me. I personally think our support for anything fortranny should be minimal.

[Stuart Campbell]

This ticket has been transferred to github issue ​2814