On 14 Nov, 16:17, DanielJohnson <[EMAIL PROTECTED]> wrote: > Thanks for telling about py2exe.
Also note that you should build an MSI installer e.g. using InnoSetup after applying py2exe. You could skip the py2exe part and only use InnoSetup to create an MSI. Most likely your client will not care if the executable file is called .py/.pyw/.pyc or .exe. Windows users are generally ignorant to the contents of the Program Files folder. They will not understand what is there and certainly not care what is there. Therefore, the only thing that really matters is to make it easy to install and run the program. That is: 1. Create an MSI that makes it easy to install the software (including runtime and dependencies). 2. Use autorun if you ship a DVD or CD-ROM. The installer should start automatically when the disc is placed in the player. 3. Make sure an icon on the "Start Menu" launches the program. If you have done that, 99.9% of all clients will be happy. The latter 0.01% is stupid enough to think it matters if the suffix of the executable is called .exe or not. Never mind these morons, just ship an .exe that does nothing except to spawn your Python program and exit. > Is there any utility that will help to make it as a .deb or .rpm file > (for Linux)? There is a tool called cx_Freeze which is similar to py2exe, except that it works on several platforms, including Linux. You will have to build the .deb or .rpm using other tools afterwards. -- http://mail.python.org/mailman/listinfo/python-list
