sikuli-driver team mailing list archive

Thread
Date

[Question #227783]: wrong behavior with sys.argv

To: sikuli-driver@xxxxxxxxxxxxxxxxxxx
From: Paraita Wohler <question227783@xxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 29 Apr 2013 16:56:10 -0000
Reply-to: question227783@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

New question #227783 on Sikuli:
https://answers.launchpad.net/sikuli/+question/227783

I'm experiencing problems with Sikuli X r930. I'm using it to automate GUI tests. Those tests are Java classes that use a ScriptRunner and everything runs fine.
Except that if I try to pass parameters (using the runPython(String[], String) method), to a Sikuli script, it works the first time, but on the second time sys.argv gets appended with my script's path.
In fact I don't even need to run my Sikuli script from Java, running this code directly in Sikuli-IDE reproduce this strange behavior:

for arg in sys.argv:
    print "ARG:" + arg

I open Sikuli-IDE, paste the code and run it.
Then I open a new Tab and paste the same code and run it.

=> sys.argv gets appended with the scripts paths.
Any idea how to prevent this or should I report it as a bug ?

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