The convenience is, that you do not have to say from sikuli import * in EVERY script (hence not in main or standalone script, that is run).
On the other hand: it conforms with Python standards, that each module has its own globals and so the user has to take care for it. --- What is so complicated ... it is indeed very complicated, to implement the same convenience for sub modules as for main scripts, since only the main script (the one, that is run) directly passes Sikuli, imported modules are directly handled by the jython interpreter. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/795491 Title: Auto import of globals in imported .sikuli scripts Status in Sikuli: Won't Fix Bug description: Right now you have to place "from sikuli.Sikuli import *" at the beginning of every imported .sikuli script. That's not user too user friendly. What is so complicated in making Sikuli globals automatically available if imported script is .sikuli script? To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/795491/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
