[jethro.fn]

As requested by big_pig and tsharju, Ensymble now supports embedding the Python runtime DLL inside an application SIS. Download the latest version of Ensymble from http://www.nbl.fi/jussi.ylanen/ensymble.html. Pre-squeezed version of Ensymble for Python v2.5 will be released shortly, after I get to a PC with Python v2.5 installed...

Some instructions: First, create your application SIS file normally. You can use the default Ensymble certificate for it even if it uses some extra capabilities, as it will be signed during the merge process. Then run:

ensymble.py mergesis --cert=mycert.cer --key=mykey.key --passphrase=12345 myapp_v1_0_0.sis PythonForS60_1_3_17_3rdEd_selfsigned.SIS myapp_standalone_v1_0_0.sis

You will get a SIS file called "myapp_standalone_v1_0_0.sis", which includes your application and the Python runtime DLL. Certificate of the Python DLL is not modified in any way. In effect, if you could install the SIS files separately, you will be able to install the combined SIS file as well.

Please note, that trying to install a SIS file containing the Python runtime DLL will fail if there is already a version of Python installed.

[tsharju]

Big thanks!

I think this improves the spreading of PyS60 applications, since for some people installing one .sis file to their phone is already almost too much. Naturally one has to make different .sis files for different feature packs, but that is the case for some of the native symbian applications as well.

- Teemu

[leban]

Is it possible (I hope it is) to use unsigned Python with ensymble and sign it at on the same run?

All the same. This is great news! Thanks!

[jethro.fn]

Originally Posted by leban

Is it possible (I hope it is) to use unsigned Python with ensymble and sign it at on the same run?

Not at the same run. Due to the way SISX files are structured, only the "outermost" SIS needs re-signing when adding embedded SIS files. In other words, embedded SIS files are contained in such a way that their signatures stay valid. This is good, because you can then embed SIS files that have capabilities which mere mortals can never acquire...

So, first create your signed Python SIS ("ensymble.py signsis ...") and then embed it ("ensymble.py mergesis ...").