[Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-21 Thread forrest
New question #265660 on Sikuli: https://answers.launchpad.net/sikuli/+question/265660 Sorry if this has been answered, but I have looked and cannot find an answer for recent builds. My imports worked all along until I upgraded to the most recent version. Running windows7pro. Referencing the Set

Re: [Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-22 Thread 皇甫春峰
Question #265660 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265660 皇甫春峰 posted a new comment: Hi forrest: I've met the same problem with sikuli, I've add my xxx.py in the same path with sikuli. If you import sikuli successfully, there will be some stdout in command-line

Re: [Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-22 Thread RaiMan
Question #265660 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265660 Status: Open => Answered RaiMan proposed the following answer: Thanks Huangfu, but what you say is related to earlier versions of Sikuli. What forrest asks is related to late versions of SikuliX version

Re: [Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-22 Thread forrest
Question #265660 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265660 Status: Answered => Open forrest is still having a problem: Thank you both for the timely response. Perhaps I am missing something but I don't see an answer that works in either of the posts. Given dev

Re: [Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-23 Thread RaiMan
Question #265660 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265660 Status: Open => Answered RaiMan proposed the following answer: as mentioned in comment #2: with Jython use JYTHONPATH instead of PYTHONPATH, since per convention PYTHONPATH is not recognised by Jython,

Re: [Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-23 Thread forrest
Question #265660 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265660 Status: Answered => Open forrest is still having a problem: IF I set JYTHONPATH then I cannot even get the IDE or the interactive jython to start - both have same error NameError: name 'SIKULIX_IS_WORKI

Re: [Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-23 Thread RaiMan
Question #265660 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265660 Status: Open => Needs information RaiMan requested more information: could please use C:\usrbin\sikulix\runsikulix.cmd -d 3 -c so the startup debug is shown and every output goes to the command line wi

Re: [Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-23 Thread forrest
Question #265660 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265660 Status: Needs information => Open forrest gave more information on the question: Re: "...could you please..." #6 == Fresh Win Command Console == Microsoft