Python import statement from MantidPlot broken

[Mathieu Doucet]

I noticed that importing python modules that live in another file doesn't always work when the importing code is executed within MantidPlot.

I will commit example code and refer to this ticket.

[Mathieu Doucet]

(In [5299]) Example python code that should work within MantidPlot. Re #1415

[Mathieu Doucet]

Run execute_test.py in the changeset 5299 (above). It works within vanilla python, but doesn't within MantidPlot. This was tested both under Ubuntu 10 and Mac OS X v10.6.

[Mathieu Doucet]

Note that you have to move the two files above elsewhere on your file system to see the problem. The problem is that the user expects the directory containing a loaded python script to be added to the python path. As it is, the two example files are already on the python path.

[Mathieu Doucet]

(In [5312]) Now that we know what the problem is we don't need those examples. Adding the file directory to the python path when loading from MantidPlot seems like the solution. Re #1415

[Martyn Gigg]

(In [7278]) Update MantidPlot scripting environment to add the path of a script to its sys.path when opened. This fixes the problem with importing modules in the same directory as a open script but outside the Mantid path. Re #1415

[Janik Zikovsky]

Tested working in MantidPlot.

[Stuart Campbell]

This ticket has been transferred to github issue ​2262