Use of the additional .py file created on export executable

Asked by Ruben on 2015-11-19

When my team exports an executable of a .sikuli script, besides creating the .skl file, the IDE creates a .py file with its named being a composition of the .sikuli folder complete name and the .sikuli folder without the .sikuli extension. It contains the exact python script of the sikuli script created by the user.

For example:
TestSomething.sikuli (project) (generated file)

I've seen the code and the export action creates that file, we tried to execute our tests deleting that files and we found they are, in our terms, useless, so maybe that files were created to be used in development phase.

So my question is, this files are needed by sikuli, if they are useless, can you, please, remove the line in the IDE code were they are created?

Thank you very much and keep working.

Question information

English Edit question
Sikuli Edit question
No assignee Edit question
Last query:
Last reply:
RaiMan (raimund-hocke) said : #1

what version of SikuliX ?

BTW: why do you use this feature (simply a zipped version of the respective .sikuli folder)?

Ruben (rrodriguez-k) said : #2

We are using 1.1.0 (2015-10-05_17:07) version of Sikulix, we just downloaded the last version in

We use this feature just because Sikuli IDE allows us to and it's an automated process (creating the zipped version of the respective .sikuli folder and changing its extension to .skl), it's easier to our QA team to execute those tests out of the IDE.

RaiMan (raimund-hocke) said : #3

ok, thanks.

I made it a bug and will check it asap.
Please follow the bug.

Ruben (rrodriguez-k) said : #4

Your wellcome and thank you :)