sikuli-driver team mailing list archive

Thread
Date

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

To: sikuli-driver@xxxxxxxxxxxxxxxxxxx
From: RaiMan <question265660@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 22 Apr 2015 09:11:49 -0000
Reply-to: question265660@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

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 1.1.0,
where indeed some things have changed internally, that might lead to
different behaviour (which would be a bug).

I just tested on a Win7-64 with Java 7 and the latest build from today:
- a PYTHONPATH in environment is not recognised (according to the rules: for Jython (Sikuli) use JYTHONPATH)
- -Dpython.path=something is recognised and gets entry[0] in sys.path

there is another question where I currently try to sort out and support all options available for Jython to get something on sys.path (either forefront or at runTime):
https://bugs.launchpad.net/sikuli/+bug/1312239

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.