Hi,
Some more comments
1) I would not call py2exe a distribution application.
py2exe creates from (a) python script(s) an executable
for windows. It also provides also all the needed libraries
to run the application.
2) In order to distribute your application, use something
like the excellent Inno Setup. With all the files prepared
by py2exe and saved in the Dist directory, Inno Setup lets
you create a setup.exe, you can distribute.
Beside this, Inno Setup lets you add an icon for your
application. This can not be done with py2exe.
You can also include other files like readme.txt and/or
changes.txt, ...
The doodle subdirectory in the wxPython directory
contains a Inno Setup script, a file with the extension
.iss
3) As Jaime Wyant rightly said: Those files are very
wxWindows / Python centric. Do not put them in
any windows system subdirectory, but keep them
in the dir containing the exe.
From you mail, I can see, you are using wxPython 2.3.2.n
and python 2.1.n. (python21.dll and wxmsw232.dll)
4) In my opinion, this is a great strength of
python/wxPython.
You can have different versions of the same application
with different (updated) wxmsw* and *.pyd libraries.
You can put all these files onto a cd or a zip disk and
run the application from there. The application must
not be installed.
You may argue the wx*.dll is large, but I think today
it's no more a problem.
5) To summarize
- create an exe with py2exe
- create a distribution file, setup.exe, with Inno Setup
- distribute your setup.exe
6) Example
My psi baby,
http://www.chez.com/spinecho/pypsi/pagpypsi.htm
Jean-Michel Fauth, Switzerland
Thanks.
Yes, the size of wx* would not be a turn off if I created a large and
complex application. So I guess I have to make large application if I want
to distribute python exe files created by py2exe 
So I concluded that if I want to make an exe application distribution, I
have to put that wx* files in
a sama directory with the main application.
Mico Siahaan
···
--------------------------
mico@intermatik.co.id
Mobile ph. 08179997828
-------Original Message-------
From: wxPython-users@lists.wxwindows.org
Date: Friday, June 27, 2003 1:53:59 AM
To: wxPython-users@lists.wxwindows.org
Subject: RE: [wxPython-users] Distributing application newbie
Hi,
Some more comments
1) I would not call py2exe a distribution application.
py2exe creates from (a) python script(s) an executable
for windows. It also provides also all the needed libraries
to run the application.
2) In order to distribute your application, use something
like the excellent Inno Setup. With all the files prepared
by py2exe and saved in the Dist directory, Inno Setup lets
you create a setup.exe, you can distribute.
Beside this, Inno Setup lets you add an icon for your
application. This can not be done with py2exe.
You can also include other files like readme.txt and/or
changes.txt, ...
The doodle subdirectory in the wxPython directory
contains a Inno Setup script, a file with the extension
..iss
3) As Jaime Wyant rightly said: Those files are very
wxWindows / Python centric. Do not put them in
any windows system subdirectory, but keep them
in the dir containing the exe.
From you mail, I can see, you are using wxPython 2.3.2.n
and python 2.1.n. (python21.dll and wxmsw232.dll)
4) In my opinion, this is a great strength of
python/wxPython.
You can have different versions of the same application
with different (updated) wxmsw* and *.pyd libraries.
You can put all these files onto a cd or a zip disk and
run the application from there. The application must
not be installed.
You may argue the wx*.dll is large, but I think today
it's no more a problem.
5) To summarize
- create an exe with py2exe
- create a distribution file, setup.exe, with Inno Setup
- distribute your setup.exe
6) Example
My psi baby,
http://www.chez.com/spinecho/pypsi/pagpypsi.htm
Jean-Michel Fauth, Switzerland
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org
.
<snip>
Beside this, Inno Setup lets you add an icon for your
application. This can not be done with py2exe.
<snap>
Actually wrong. Just use the --icon option. It got to be a .ico file though.
python setup.py py2exe --icon bla.ico
Will do the trick.
If you have a smaller project where you don't want to go through the Inno
setup script thing you can check out http://installbase.sourceforge.net/
Works quite nice (more stable under Linux) and lets you "cross create"
installers. I use it for a smaller thing where I create the installer on a
linux box.
It's not as mature as Inno, but it does an easy graphical way of creating
installers.
UC
···
--
Open Source Solutions 4U, LLC 2570 Fleetwood Drive
Phone: +1 650 872 2425 San Bruno, CA 94066
Cell: +1 650 302 2405 United States
Fax: +1 650 872 2417