sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #03235
[Bug 795491] [NEW] Auto import of globals in imported .sikuli scripts
Public bug reported:
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?
** Affects: sikuli
Importance: Undecided
Status: New
--
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:
New
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
Follow ups
References