[noreli]

Py2sis was working very well on the 2nd ED (SDK V2).
I installed the new SDK.
Then I had Py2sis works for 3rd (after a small fight but that's OK).

But when I wanted to update my software for 2ndED it was not working any more !

Error message is :

'No vendor Names found' 
'bad langage count'

I suppose it's due to the new SDK installation.
I read few topics about that in C++, but I don't know how to apply it to python.
I tried to find other py2sis.exe and py2sis.py on my hard-disk, but it lokks like they were replaced...

What is the best way to proceed ?
- reinstall the SDK on different computer to do have a solution ?
- reinstall some added files smartly somewhere ?
- other ?

Thanks for your help.

[noreli]

I have an idea to have a very simple generic solution:
I create an almost empty .SIS with a single .py file (code below).
These file is acting as an empty nuts that call a .pyc remote file in a path you can choose. These remote .pyc does all the job.

I already experimented these kind of trick, it's working fairly well. When you want to upgrade your app, you just have to push new .py* file on your app directory (with a sync file it can even be automated). You can improve it with a .INI file that gives the path and the starting external module.

import sys
sys.path('c:\my_path_app')
import MyStartModule

In these code I import MyStartModule.py which is located in c:\my_path_app.

But my probleme remains...

My py2sis is not working any more in the 2nd ed. My .SIS was replaced by a 3rd edition one.

Reinstallation on a second computer ?

[aaaaapo]

Originally Posted by noreli

I have an idea to have a very simple generic solution:
I create an almost empty .SIS with a single .py file (code below).
These file is acting as an empty nuts that call a .pyc remote file in a path you can choose. These remote .pyc does all the job.

The remote code could also come from the server when your application starts...