Question #233331 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233331
Sunil posted a new comment: Finally, the issue got resolved from the clues RaiMan posted on linked bug 1210474. "a Sikuli script should not be named as a Python module, when this Python module should be imported." I didn't had any script with name "xml.sikuli" but was not noticing the another script having name with another Python module "struct.sikuli". The xml parser script was running successfully if placed into some other location, but the moment it put into the library of all other scripts (where the culprit struct.sikuli was lying) it started throwing Parser not found error. Even if you create a dummy directory with this name (struct.sikuli) the xml parsing script (as posted into initial post) will fail with parser not found error, which otherwise works fine! Thanks for all your support, it got resolved finally. -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
