Update from ... import statements in ISIS_Powder units

[DannyHindson]

There are various from ... import statements in the ISIS_Powder units that rely on the mantid-scripts.pth file having been processed so that all of the scripts subdirectories (eg Diffraction, Engineering etc) are present on the sys path. These statements generate red highlights in PyCharm because the .pth file is only processed at run time whenever the mantid.simpleapi is imported:

This means there are various distracting errors highlighted by PyCharm and it also means that if you have a unit that doesn't contain import mantid.simpleapi the from ... import statement will fail (even though the same statement works at run time in another unit)

If the module paths were extended with a Diffraction prefix (eg from Diffraction.isis_powder import X) I think the PyCharm warnings would go away and this would be a lot more transparent

[stale]

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs.
Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point.
If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer.
To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

[DannyHindson]

Keep open

[stale]

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs.
Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point.
If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer.
To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

[sf1919]

Keep open