Ticket #1488 (closed: fixed)

Opened 10 years ago

Last modified 5 years ago

Importing MantidFramework defines variables that should be private

Reported by: Martyn Gigg Owned by: Martyn Gigg
Priority: major Milestone: Iteration 24
Component: Keywords:
Cc: Blocked By:
Blocking: Tester: Mathieu Doucet

Description

Executing 

from MantidFramework import *
print file
print direcs

shows that some variables used in the MantidFramework module are not kept in that scope as they should be.

Change History

comment:1 Changed 10 years ago by Martyn Gigg

  • Status changed from new to accepted

comment:2 Changed 10 years ago by Martyn Gigg

(In [5703]) Fix problem with exporting variables that should remain private to the module, they cause confusion otherwise. Re #1488

comment:3 Changed 10 years ago by Martyn Gigg

  • Status changed from accepted to verify

comment:4 Changed 10 years ago by Martyn Gigg

  • Status changed from verify to reopened

comment:5 Changed 10 years ago by Martyn Gigg

(In [5745]) Fix for incorrect module search path when importing mantidsimple. Re #1488

comment:6 Changed 10 years ago by Martyn Gigg

(In [5747]) Fix for initialisation order in Python Framework file. Re #1488

comment:7 Changed 10 years ago by Martyn Gigg

(In [5759]) Fix for module search path on Linux when initialising framework. Re #1488

comment:8 Changed 10 years ago by Martyn Gigg

  • Status changed from reopened to accepted

comment:9 Changed 10 years ago by Martyn Gigg

  • Status changed from accepted to verify

comment:10 Changed 10 years ago by Nick Draper

  • Resolution set to fixed

fill in missing resolution

comment:11 Changed 10 years ago by Mathieu Doucet

  • Status changed from verify to verifying
  • Tester set to Mathieu Doucet

comment:12 Changed 10 years ago by Mathieu Doucet

  • Status changed from verifying to closed

Went through the refactor, looks sane and fixes the problem described above.

comment:13 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​2336

Note: See TracTickets for help on using tickets.