That is very close to what I have being doing, however I was unable to enclose a bmp or another file for that matter in the exe. I used both DATA and BINARY key words with no luck. I checked what was in the package and there were there. I guess for some reason it could not locate then when executed. I used snap 274 if I remember correctly.
I am not too sure I am explaining my question correctly though. I have not problem creating and distributing my python/wxpython scripts in exe (stand-a-lone) except for what I have described above. I am worrying that when the py script is run I am leaving behind files. That the components of my stand-alone exe is somehow coming out of the exe (PyInstaller) and being installed. My setup exe is not what's is bothering me although I do like the your suggestion and have just been tinkering with it. It is cool stuff and much better then what I have been using. Thx "James Stroud" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > LittlePython wrote: > > Thx for the tip. > > > > I am referring more to the use of PyInstaller or py2exe. Packages that > > create exe files that basically have your py script and a small py > > interpreter all rolled up into one. This way py does not need to be > > installed on a system to execute a py script. I am being advised that python > > is installed onto systems (windows) it should not be on. I am new to python > > and these types of packages and am not too sure how dumb a question this > > really is.. but can these packages bleed out files, dll, exe ect. to systems > > they are run on? > > They don't have to "bleed" anything. Everything, including the python > interpreter, and 3rd party libraries can be included in a single > executable. Here is an example script for pyinstaller that rolls > evertyhing into one file (this is what I use to roll up my passerby > program at passerby.souceforge.net): > > > setenv TEMP temp > > set pythonexe='c:/Python23-Enthought/python' > set pbydir='z:/Code/pby/current/' > > rm *.pyc > > rm -rf ./temp/ ./passerby/ > mkdir temp > > $pythonexe Configure.py > $pythonexe Makespec.py --onefile --tk --noconsole \ > --icon $pbydir/../icons/passerby.ico \ > $pbydir/passerby.py passerby/passerby.spec > $pythonexe Build.py passerby/passerby.spec > > > You can control installation with innosetup. > > James > > -- > James Stroud > UCLA-DOE Institute for Genomics and Proteomics > Box 951570 > Los Angeles, CA 90095 > > http://www.jamesstroud.com/ -- http://mail.python.org/mailman/listinfo/python-list
