Ticket #2944 (closed: fixed)
Review of MantidPlot's embedded Python environment
Reported by: | Martyn Gigg | Owned by: | Martyn Gigg |
---|---|---|---|
Priority: | major | Milestone: | Release 2.1 |
Component: | Mantid | Keywords: | |
Cc: | doucetm@… | Blocked By: | |
Blocking: | Tester: | Stuart Campbell |
Description
The embedded Python environment in MantidPlot is creaking under the strain at the moment. The fundamental issue is that it was designed for quick, single-threaded scripts to run to interactively control GUI elements.
The code is quite fragile and we keep seeing issues, i.e. #2850, #2562 and #2556, which are fundamentally related to this. Written correctly we should be able to execute concurrent Python code, currently this seems to be hit-and-miss as to whether it will work.
The environment could do with a review now that we know how we use it and it would also benefit our custom interfaces if the enviroment were moved out of MantidPlot so that they could link directly with the embedded interpreter rather than communicating with a string as they do currently.
Change History
comment:2 Changed 9 years ago by Martyn Gigg
- Status changed from new to accepted
- Owner set to Martyn Gigg
comment:3 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 30 to Iteration 31
Bulk move of tickets to iteration 31 at the iteration 30 code freeze
comment:4 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 32 to Iteration 33
Moved to iteration 33 at iteration 32 code freeze
comment:5 Changed 9 years ago by Martyn Gigg
- Status changed from accepted to verify
- Resolution set to fixed
See #5006. Decision has been made to properly thread the execution of the scripts
"New" tickets moved at the code freeze of iteration 29