From: Dick M. <rd...@rc...> - 2006-08-30 03:48:10
|
<html> <body> OK, I edited the path, adding E:\Python24\, and rebooted (did I need to?).<br><br> This time, with both my app and setup.py in E:\Python24\For_py2exe_setup.py, py2exe worked and created an exe that worked. However, when I copied it to my desktop I found that all that happened when clicking on it was a quick flash of some window.<br><br> Then I thought I'd try a simple script, helloWorld.py . the exe was created OK, but when moving it out of dist into any other folder, again got that flashing window. Here's the script:<br><br> ========================<br> # Hello World!<br> print "Hello, World!"<br><br> raw_input("\n\nPress the enter key to exit.")<br> =========================<br><br> I tried to run this at the command line, with these results:<br><br> =============================<br> E:\Python24\For_py2exe_setup.py\dist>helloWorld.exe<br> Hello, World!<br><br> <br> Press the enter key to exit.<br><br> E:\Python24\For_py2exe_setup.py\dist>cd..<br><br> E:\Python24\For_py2exe_setup.py>helloWorld.exe<br> LoadLibrary(pythondll) failedThe specified module could not be found.<br><br> E:\Python24\For_py2exe_setup.py><br> =============================<br> (see way down below for what was printed during the creation of helloWorld.exe)<br><br> <br> Here's the command line result for 2 identical copies of 1keyPress-b5.exe:<br><br> ==========================<br> E:\Python24\dist>1keyPress-b5.exe<br><br> The program has started.<br><br> press Space to get first and sub<br> press h to print "Hello".<br> press t to print the current tim<br> press s to see how many spins ha<br> Press q to quit.<br><br> <br> 151541 spins<br> Time was 2.641 seconds<br> Spin rate was 57380 per second<br><br> Hello<br><br> The current time is 20:12:41<br><br> 750238 spins<br> Time was 13.27 seconds<br> Spin rate was 56558 per second<br><br> The current time is 20:12:48<br><br> 418276 spins<br> Time was 7.329 seconds<br> Spin rate was 57071 per second<br> Bye.<br><br> <br> E:\Python24\Myscripts>1keyPress-b5.exe<br> LoadLibrary(pythondll) failedThe specified module could not be found.<br> ========================================<br><br> <br> So it seems I need pythondll. I searched all of Python24, including subfolders of course. No pythondll or python.dll . What to do?<br><br> The tutorial says<br><br> ==========================<br> Now that the package has been created it is ready to test: <br><br> <pre>C:\Tutorial>cd dist C:\Tutorial\dist>hello.exe Hello World </pre>Excellent, it works!!!=============================<br><br> No mention of the need to test with the exe moved out of dist.<br><br> <br> I thought it might be useful to show what was printed during the creation of helloWorld.exe <br><br> ===============================================<br><br> E:\Python24\For_py2exe_setup.py>python setup.py py2exe<br> running py2exe<br> *** searching for required modules ***<br> *** parsing results ***<br> creating python loader for extension 'zlib'<br> creating python loader for extension 'unicodedata'<br> creating python loader for extension 'bz2'<br> *** finding dlls needed ***<br> *** create binaries ***<br> *** byte compile python files ***<br> byte-compiling E:\Python24\For_py2exe_setup.py\build\bdist.win32\winexe\temp\bz2<br> .py to bz2.pyc<br> byte-compiling E:\Python24\For_py2exe_setup.py\build\bdist.win32\winexe\temp\uni<br> codedata.py to unicodedata.pyc<br> byte-compiling E:\Python24\For_py2exe_setup.py\build\bdist.win32\winexe\temp\zli<br> b.py to zlib.pyc<br> skipping byte-compilation of E:\Python24\lib\StringIO.py to StringIO.pyc<br> skipping byte-compilation of E:\Python24\lib\UserDict.py to UserDict.pyc<br> skipping byte-compilation of E:\Python24\lib\atexit.py to atexit.pyc<br> skipping byte-compilation of E:\Python24\lib\base64.py to base64.pyc<br> skipping byte-compilation of E:\Python24\lib\codecs.py to codecs.pyc<br> skipping byte-compilation of E:\Python24\lib\copy.py to copy.pyc<br> skipping byte-compilation of E:\Python24\lib\copy_reg.py to copy_reg.pyc<br> skipping byte-compilation of E:\Python24\lib\dis.py to dis.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\__init__.py to encodings\<br> __init__.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\aliases.py to encodings\a<br> liases.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\ascii.py to encodings\asc<br> ii.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\base64_codec.py to encodi<br> ngs\base64_codec.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\big5.py to encodings\big5<br> .pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\big5hkscs.py to encodings<br> \big5hkscs.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\bz2_codec.py to encodings<br> \bz2_codec.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\charmap.py to encodings\c<br> harmap.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp037.py to encodings\cp0<br> 37.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1006.py to encodings\cp<br> 1006.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1026.py to encodings\cp<br> 1026.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1140.py to encodings\cp<br> 1140.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1250.py to encodings\cp<br> 1250.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1251.py to encodings\cp<br> 1251.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1252.py to encodings\cp<br> 1252.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1253.py to encodings\cp<br> 1253.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1254.py to encodings\cp<br> 1254.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1255.py to encodings\cp<br> 1255.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1256.py to encodings\cp<br> 1256.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1257.py to encodings\cp<br> 1257.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp1258.py to encodings\cp<br> 1258.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp424.py to encodings\cp4<br> 24.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp437.py to encodings\cp4<br> 37.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp500.py to encodings\cp5<br> 00.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp737.py to encodings\cp7<br> 37.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp775.py to encodings\cp7<br> 75.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp850.py to encodings\cp8<br> 50.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp852.py to encodings\cp8<br> 52.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp855.py to encodings\cp8<br> 55.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp856.py to encodings\cp8<br> 56.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp857.py to encodings\cp8<br> 57.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp860.py to encodings\cp8<br> 60.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp861.py to encodings\cp8<br> 61.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp862.py to encodings\cp8<br> 62.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp863.py to encodings\cp8<br> 63.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp864.py to encodings\cp8<br> 64.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp865.py to encodings\cp8<br> 65.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp866.py to encodings\cp8<br> 66.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp869.py to encodings\cp8<br> 69.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp874.py to encodings\cp8<br> 74.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp875.py to encodings\cp8<br> 75.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp932.py to encodings\cp9<br> 32.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp949.py to encodings\cp9<br> 49.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\cp950.py to encodings\cp9<br> 50.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\euc_jis_2004.py to encodi<br> ngs\euc_jis_2004.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\euc_jisx0213.py to encodi<br> ngs\euc_jisx0213.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\euc_jp.py to encodings\eu<br> c_jp.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\euc_kr.py to encodings\eu<br> c_kr.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\gb18030.py to encodings\g<br> b18030.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\gb2312.py to encodings\gb<br> 2312.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\gbk.py to encodings\gbk.p<br> yc<br> skipping byte-compilation of E:\Python24\lib\encodings\hex_codec.py to encodings<br> \hex_codec.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\hp_roman8.py to encodings<br> \hp_roman8.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\hz.py to encodings\hz.pyc<br><br> skipping byte-compilation of E:\Python24\lib\encodings\idna.py to encodings\idna<br> .pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso2022_jp.py to encoding<br> s\iso2022_jp.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso2022_jp_1.py to encodi<br> ngs\iso2022_jp_1.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso2022_jp_2.py to encodi<br> ngs\iso2022_jp_2.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso2022_jp_2004.py to enc<br> odings\iso2022_jp_2004.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso2022_jp_3.py to encodi<br> ngs\iso2022_jp_3.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso2022_jp_ext.py to enco<br> dings\iso2022_jp_ext.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso2022_kr.py to encoding<br> s\iso2022_kr.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_1.py to encodings<br> \iso8859_1.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_10.py to encoding<br> s\iso8859_10.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_11.py to encoding<br> s\iso8859_11.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_13.py to encoding<br> s\iso8859_13.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_14.py to encoding<br> s\iso8859_14.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_15.py to encoding<br> s\iso8859_15.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_16.py to encoding<br> s\iso8859_16.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_2.py to encodings<br> \iso8859_2.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_3.py to encodings<br> \iso8859_3.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_4.py to encodings<br> \iso8859_4.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_5.py to encodings<br> \iso8859_5.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_6.py to encodings<br> \iso8859_6.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_7.py to encodings<br> \iso8859_7.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_8.py to encodings<br> \iso8859_8.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\iso8859_9.py to encodings<br> \iso8859_9.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\johab.py to encodings\joh<br> ab.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\koi8_r.py to encodings\ko<br> i8_r.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\koi8_u.py to encodings\ko<br> i8_u.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\latin_1.py to encodings\l<br> atin_1.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\mac_cyrillic.py to encodi<br> ngs\mac_cyrillic.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\mac_greek.py to encodings<br> \mac_greek.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\mac_iceland.py to encodin<br> gs\mac_iceland.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\mac_latin2.py to encoding<br> s\mac_latin2.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\mac_roman.py to encodings<br> \mac_roman.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\mac_turkish.py to encodin<br> gs\mac_turkish.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\mbcs.py to encodings\mbcs<br> .pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\palmos.py to encodings\pa<br> lmos.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\ptcp154.py to encodings\p<br> tcp154.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\punycode.py to encodings\<br> punycode.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\quopri_codec.py to encodi<br> ngs\quopri_codec.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\raw_unicode_escape.py to<br> encodings\raw_unicode_escape.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\rot_13.py to encodings\ro<br> t_13.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\shift_jis.py to encodings<br> \shift_jis.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\shift_jis_2004.py to enco<br> dings\shift_jis_2004.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\shift_jisx0213.py to enco<br> dings\shift_jisx0213.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\string_escape.py to encod<br> ings\string_escape.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\tis_620.py to encodings\t<br> is_620.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\undefined.py to encodings<br> \undefined.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\unicode_escape.py to enco<br> dings\unicode_escape.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\unicode_internal.py to en<br> codings\unicode_internal.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\utf_16.py to encodings\ut<br> f_16.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\utf_16_be.py to encodings<br> \utf_16_be.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\utf_16_le.py to encodings<br> \utf_16_le.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\utf_7.py to encodings\utf<br> _7.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\utf_8.py to encodings\utf<br> _8.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\uu_codec.py to encodings\<br> uu_codec.pyc<br> skipping byte-compilation of E:\Python24\lib\encodings\zlib_codec.py to encoding<br> s\zlib_codec.pyc<br> skipping byte-compilation of E:\Python24\lib\getopt.py to getopt.pyc<br> skipping byte-compilation of E:\Python24\lib\inspect.py to inspect.pyc<br> skipping byte-compilation of E:\Python24\lib\linecache.py to linecache.pyc<br> skipping byte-compilation of E:\Python24\lib\macpath.py to macpath.pyc<br> skipping byte-compilation of E:\Python24\lib\ntpath.py to ntpath.pyc<br> skipping byte-compilation of E:\Python24\lib\opcode.py to opcode.pyc<br> skipping byte-compilation of E:\Python24\lib\os.py to os.pyc<br> skipping byte-compilation of E:\Python24\lib\os2emxpath.py to os2emxpath.pyc<br> skipping byte-compilation of E:\Python24\lib\popen2.py to popen2.pyc<br> skipping byte-compilation of E:\Python24\lib\posixpath.py to posixpath.pyc<br> skipping byte-compilation of E:\Python24\lib\quopri.py to quopri.pyc<br> skipping byte-compilation of E:\Python24\lib\re.py to re.pyc<br> skipping byte-compilation of E:\Python24\lib\repr.py to repr.pyc<br> skipping byte-compilation of E:\Python24\lib\sre.py to sre.pyc<br> skipping byte-compilation of E:\Python24\lib\sre_compile.py to sre_compile.pyc<br> skipping byte-compilation of E:\Python24\lib\sre_constants.py to sre_constants.p<br> yc<br> skipping byte-compilation of E:\Python24\lib\sre_parse.py to sre_parse.pyc<br> skipping byte-compilation of E:\Python24\lib\stat.py to stat.pyc<br> skipping byte-compilation of E:\Python24\lib\string.py to string.pyc<br> skipping byte-compilation of E:\Python24\lib\stringprep.py to stringprep.pyc<br> skipping byte-compilation of E:\Python24\lib\token.py to token.pyc<br> skipping byte-compilation of E:\Python24\lib\tokenize.py to tokenize.pyc<br> skipping byte-compilation of E:\Python24\lib\traceback.py to traceback.pyc<br> skipping byte-compilation of E:\Python24\lib\types.py to types.pyc<br> skipping byte-compilation of E:\Python24\lib\warnings.py to warnings.pyc<br> *** copy extensions ***<br> *** copy dlls ***<br> copying E:\Python24\lib\site-packages\py2exe\run.exe -> E:\Python24\For_py2exe_s<br> etup.py\dist\helloWorld.exe<br><br> *** binary dependencies ***<br> Your executable(s) also depend on these dlls which are not included,<br> you may or may not need to distribute them.<br><br> Make sure you have the license if you distribute any of them, and<br> make sure you don't distribute files belonging to the operating system.<br><br> ADVAPI32.dll - C:\WINDOWS\system32\ADVAPI32.dll<br> USER32.dll - C:\WINDOWS\system32\USER32.dll<br> SHELL32.dll - C:\WINDOWS\system32\SHELL32.dll<br> KERNEL32.dll - C:\WINDOWS\system32\KERNEL32.dll<br><br> <br> Press the enter key to exit.<br><br> E:\Python24\For_py2exe_setup.py><br> =============================================<br><br> Dick<br><br> <br> </body> <br> </html> |
From: John M. <sjm...@le...> - 2006-08-30 05:43:13
|
On 30/08/2006 1:47 PM, Dick Moores wrote: > OK, I edited the path, adding E:\Python24\, and rebooted (did I need to?). No, you didn't need to reboot. > > This time, with both my app and setup.py in > E:\Python24\For_py2exe_setup.py, py2exe worked and created an exe that > worked. However, when I copied it to my desktop I found that all that > happened when clicking on it was a quick flash of some window. > The "dist" directory contains the files [plural] that need to be distributed. Copying the exe is not enough. You may wish to read the FAQ: http://www.py2exe.org/index.cgi/FAQ You may wish to put a *shortcut* to whatever.exe on your desktop; that will work, provided of course that the other files are in the same directory as the exe. > Then I thought I'd try a simple script, helloWorld.py . the exe was > created OK, but when moving it out of dist into any other folder, again > got that flashing window. Here's the script: > > ======================== > # Hello World! > print "Hello, World!" > > raw_input("\n\nPress the enter key to exit.") > ========================= > > I tried to run this at the command line, with these results: > > ============================= > E:\Python24\For_py2exe_setup.py\dist>helloWorld.exe > Hello, World! > > > Press the enter key to exit. > > E:\Python24\For_py2exe_setup.py\dist>cd.. > > E:\Python24\For_py2exe_setup.py>helloWorld.exe > LoadLibrary(pythondll) failedThe specified module could not be found. > > E:\Python24\For_py2exe_setup.py> > ============================= > (see way down below for what was printed during the creation of > helloWorld.exe) > > > Here's the command line result for 2 identical copies of 1keyPress-b5.exe: > > ========================== > E:\Python24\dist>1keyPress-b5.exe > > The program has started. > > press Space to get first and sub [snip] > > E:\Python24\Myscripts>1keyPress-b5.exe > LoadLibrary(pythondll) failedThe specified module could not be found. You may wish to raise an enhancement request for a more explicit error message. Evidently "pythondll" is a generic term, not the name of a particular file. > ======================================== > > > So it seems I need pythondll. I searched all of Python24, including > subfolders of course. No pythondll or python.dll . What to do? > Try typing ......\dist\1keyPress-b5.exe HTH, John |
From: Dick M. <rd...@rc...> - 2006-08-30 09:43:34
|
At 10:43 PM 8/29/2006, John Machin wrote: >On 30/08/2006 1:47 PM, Dick Moores wrote: > > OK, I edited the path, adding E:\Python24\, and rebooted (did I need to?). > >No, you didn't need to reboot. OK, thanks. > > This time, with both my app and setup.py in > > E:\Python24\For_py2exe_setup.py, py2exe worked and created an exe that > > worked. However, when I copied it to my desktop I found that all that > > happened when clicking on it was a quick flash of some window. > > > >The "dist" directory contains the files [plural] that need to be >distributed. Copying the exe is not enough. You may wish to read the >FAQ: http://www.py2exe.org/index.cgi/FAQ >You may wish to put a *shortcut* to whatever.exe on your desktop; that >will work, provided of course that the other files are in the same >directory as the exe. I did skim the FAQ before, but what it was saying didn't register with me. I was laboring under the misapprehension that py2exe, when it worked, would turn a .py into a .exe that I could email to someone or hand to him on a disk, and he could run it as is. So, now that I know that isn't the case, I'm a bit less interested in learning to use py2exe. If I have a good Python program, I'm happy running it as a .py. I don't see the need for the .exe at all. Now, I'm sure I'm wrong about this, but don't know where. There must be a way to create a nice package for a friend that contains the .exe and all the other goodies necessary to run it. Where is this info? Why is this so hard? Or maybe I should just continue learning Python and get back to this packaging later. > > Then I thought I'd try a simple script, helloWorld.py . the exe was > > created OK, but when moving it out of dist into any other folder, again > > got that flashing window. Here's the script: > > > > ======================== > > # Hello World! > > print "Hello, World!" > > > > raw_input("\n\nPress the enter key to exit.") > > ========================= > > > > I tried to run this at the command line, with these results: > > > > ============================= > > E:\Python24\For_py2exe_setup.py\dist>helloWorld.exe > > Hello, World! > > > > > > Press the enter key to exit. > > > > E:\Python24\For_py2exe_setup.py\dist>cd.. > > > > E:\Python24\For_py2exe_setup.py>helloWorld.exe > > LoadLibrary(pythondll) failedThe specified module could not be found. > > > > E:\Python24\For_py2exe_setup.py> > > ============================= > > (see way down below for what was printed during the creation of > > helloWorld.exe) > > > > > > Here's the command line result for 2 identical copies of 1keyPress-b5.exe: > > > > ========================== > > E:\Python24\dist>1keyPress-b5.exe > > > > The program has started. > > > > press Space to get first and sub >[snip] > > > > E:\Python24\Myscripts>1keyPress-b5.exe > > LoadLibrary(pythondll) failedThe specified module could not be found. > >You may wish to raise an enhancement request for a more explicit error >message. Evidently "pythondll" is a generic term, not the name of a >particular file. After reading around a bit I came across the filename python24.dll. That's probably what's meant in my case. I found 2 of them. One in E:\Python24\dist and one in E:\Python24\For_py2exe_setup.py\dist . I put another copy in E:\Python24\Myscripts and now the copy of 1keyPress-b5.exe that's in there runs fine! I had put a couple of exe's on my desktop--they didn't work there, but after putting another copy of python24.dll there, they work fine as well. I sent a couple of exe's that I had, along with python24.dll, to a friend with a Win 2000 box. The results were uneven. One, 1keyPress-b5.exe, worked even though reporting this error: "Traceback (most recent call last): File "E:\Python24\lib\site-packages\py2exe\boot_common.py", line 92, in ImportError: No module named linecache" The other exe failed. I later realized that I got the same error when running 1keyPress-b5.exe in a folder with python24.dll, but without library.zip (which py2exe creates in dist folders). When I added library.zip to that folder, 1keyPress-b5.exe ran without error. I've subsequently sent my friend library.zip and expect (hope) both exe's will run fine for him. So it may be that I can now make a kind of zipped up package to send out--exe's plus python24.dll and library.zip. Does this make sense? Dick |
From: jim-on-linux <in...@ve...> - 2006-08-30 18:27:58
|
On Wednesday 30 August 2006 05:43, Dick Moores wrote: > I did skim the FAQ before, but what it was > saying didn't register with me. I was laboring > under the misapprehension that py2exe, when it > worked, would turn a .py into a .exe that I > could email to someone or hand to him on a > disk, and he could run it as is. So, now that I > know that isn't the case, I'm a bit less > interested in learning to use py2exe. If I > have a good Python program, I'm happy running > it as a .py. I don't see the need for the .exe > at all. Dick, Check out website http://www.inqvista.com Download the zipped version of inqVista, v1.7 Open the package and see how and why py2exe is necessary for Windows users and how you can send those files that make your package work. If all of the users you know have Python installed, you don't need py2exe. If you know people that use win95, win98, 2000, X and all that other stuff from MS and they don't have python, you will understand why py2exe is invaluable. Those products built with py2exe are more professional and easier to distribute. jim-on-linux > > Now, I'm sure I'm wrong about this, but don't > know where. There must be a way to create a > nice package for a friend that contains the > .exe and all the other goodies necessary to run > it. Where is this info? Why is this so hard? > > Or maybe I should just continue learning Python > and get back to this packaging later. > > > > Then I thought I'd try a simple script, > > > helloWorld.py . the exe was created OK, but > > > when moving it out of dist into any other > > > folder, again got that flashing window. > > > Here's the script: > > > > > > ======================== > > > # Hello World! > > > print "Hello, World!" > > > > > > raw_input("\n\nPress the enter key to > > > exit.") ========================= > > > > > > I tried to run this at the command line, > > > with these results: > > > > > > ============================= > > > E:\Python24\For_py2exe_setup.py\dist>helloW > > >orld.exe Hello, World! > > > > > > > > > Press the enter key to exit. > > > > > > E:\Python24\For_py2exe_setup.py\dist>cd.. > > > > > > E:\Python24\For_py2exe_setup.py>helloWorld. > > >exe LoadLibrary(pythondll) failedThe > > > specified module could not be found. > > > > > > E:\Python24\For_py2exe_setup.py> > > > ============================= > > > (see way down below for what was printed > > > during the creation of helloWorld.exe) > > > > > > > > > Here's the command line result for 2 > > > identical copies of 1keyPress-b5.exe: > > > > > > ========================== > > > E:\Python24\dist>1keyPress-b5.exe > > > > > > The program has started. > > > > > > press Space to get first and sub > > > >[snip] > > > > > E:\Python24\Myscripts>1keyPress-b5.exe > > > LoadLibrary(pythondll) failedThe specified > > > module could not be found. > > > >You may wish to raise an enhancement request > > for a more explicit error message. Evidently > > "pythondll" is a generic term, not the name > > of a particular file. > > After reading around a bit I came across the > filename python24.dll. That's probably what's > meant in my case. I found 2 of them. One in > E:\Python24\dist and one in > E:\Python24\For_py2exe_setup.py\dist . I put > another copy in E:\Python24\Myscripts and now > the copy of 1keyPress-b5.exe that's in there > runs fine! I had put a couple of exe's on my > desktop--they didn't work there, but after > putting another copy of python24.dll there, > they work fine as well. > > I sent a couple of exe's that I had, along with > python24.dll, to a friend with a Win 2000 box. > The results were uneven. One, 1keyPress-b5.exe, > worked even though reporting this error: > > "Traceback (most recent call last): > File > "E:\Python24\lib\site-packages\py2exe\boot_comm >on.py", line 92, in ImportError: No module named > linecache" > > The other exe failed. > > I later realized that I got the same error when > running 1keyPress-b5.exe in a folder with > python24.dll, but without library.zip (which > py2exe creates in dist folders). When I added > library.zip to that folder, 1keyPress-b5.exe > ran without error. I've subsequently sent my > friend library.zip and expect (hope) both exe's > will run fine for him. > > So it may be that I can now make a kind of > zipped up package to send out--exe's plus > python24.dll and library.zip. Does this make > sense? > > Dick > > > > > ----------------------------------------------- >-------------------------- Using Tomcat but need > to do more? Need to support web services, > security? Get stuff done quickly with > pre-integrated technology to make your job > easier Download IBM WebSphere Application > Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120 >709&bid=263057&dat=121642 > _______________________________________________ > Py2exe-users mailing list > Py2...@li... > https://lists.sourceforge.net/lists/listinfo/py >2exe-users |
From: Dick M. <rd...@rc...> - 2006-08-31 09:47:47
|
At 11:38 AM 8/30/2006, jim-on-linux wrote: >On Wednesday 30 August 2006 05:43, Dick Moores >wrote: > > > I did skim the FAQ before, but what it was > > saying didn't register with me. I was laboring > > under the misapprehension that py2exe, when it > > worked, would turn a .py into a .exe that I > > could email to someone or hand to him on a > > disk, and he could run it as is. So, now that I > > know that isn't the case, I'm a bit less > > interested in learning to use py2exe. If I > > have a good Python program, I'm happy running > > it as a .py. I don't see the need for the .exe > > at all. > > >Dick, > >Check out website http://www.inqvista.com >Download the zipped version of inqVista, v1.7 >Open the package and see how and why py2exe is >necessary for Windows users and how you can send >those files that make your package work. Jim, I did take a look. If py2exe can figure out what a package needs to work on Windows box-without-Python, and put them all into a folder (dist?) ready to be zipped, please tell me how to use it that way. So far, I haven't figured that out. Thanks, Dick Moores >If all of the users you know have Python >installed, you don't need py2exe. If you know >people that use win95, win98, 2000, X and all >that other stuff from MS and they don't have >python, you will understand why py2exe is >invaluable. > >Those products built with py2exe are more >professional and easier to distribute. > >jim-on-linux > > > > > > > > > > Now, I'm sure I'm wrong about this, but don't > > know where. There must be a way to create a > > nice package for a friend that contains the > > .exe and all the other goodies necessary to run > > it. Where is this info? Why is this so hard? > > > > Or maybe I should just continue learning Python > > and get back to this packaging later. > > > > > > Then I thought I'd try a simple script, > > > > helloWorld.py . the exe was created OK, but > > > > when moving it out of dist into any other > > > > folder, again got that flashing window. > > > > Here's the script: > > > > > > > > ======================== > > > > # Hello World! > > > > print "Hello, World!" > > > > > > > > raw_input("\n\nPress the enter key to > > > > exit.") ========================= > > > > > > > > I tried to run this at the command line, > > > > with these results: > > > > > > > > ============================= > > > > E:\Python24\For_py2exe_setup.py\dist>helloW > > > >orld.exe Hello, World! > > > > > > > > > > > > Press the enter key to exit. > > > > > > > > E:\Python24\For_py2exe_setup.py\dist>cd.. > > > > > > > > E:\Python24\For_py2exe_setup.py>helloWorld. > > > >exe LoadLibrary(pythondll) failedThe > > > > specified module could not be found. > > > > > > > > E:\Python24\For_py2exe_setup.py> > > > > ============================= > > > > (see way down below for what was printed > > > > during the creation of helloWorld.exe) > > > > > > > > > > > > Here's the command line result for 2 > > > > identical copies of 1keyPress-b5.exe: > > > > > > > > ========================== > > > > E:\Python24\dist>1keyPress-b5.exe > > > > > > > > The program has started. > > > > > > > > press Space to get first and sub > > > > > >[snip] > > > > > > > E:\Python24\Myscripts>1keyPress-b5.exe > > > > LoadLibrary(pythondll) failedThe specified > > > > module could not be found. > > > > > >You may wish to raise an enhancement request > > > for a more explicit error message. Evidently > > > "pythondll" is a generic term, not the name > > > of a particular file. > > > > After reading around a bit I came across the > > filename python24.dll. That's probably what's > > meant in my case. I found 2 of them. One in > > E:\Python24\dist and one in > > E:\Python24\For_py2exe_setup.py\dist . I put > > another copy in E:\Python24\Myscripts and now > > the copy of 1keyPress-b5.exe that's in there > > runs fine! I had put a couple of exe's on my > > desktop--they didn't work there, but after > > putting another copy of python24.dll there, > > they work fine as well. > > > > I sent a couple of exe's that I had, along with > > python24.dll, to a friend with a Win 2000 box. > > The results were uneven. One, 1keyPress-b5.exe, > > worked even though reporting this error: > > > > "Traceback (most recent call last): > > File > > "E:\Python24\lib\site-packages\py2exe\boot_comm > >on.py", line 92, in ImportError: No module named > > linecache" > > > > The other exe failed. > > > > I later realized that I got the same error when > > running 1keyPress-b5.exe in a folder with > > python24.dll, but without library.zip (which > > py2exe creates in dist folders). When I added > > library.zip to that folder, 1keyPress-b5.exe > > ran without error. I've subsequently sent my > > friend library.zip and expect (hope) both exe's > > will run fine for him. > > > > So it may be that I can now make a kind of > > zipped up package to send out--exe's plus > > python24.dll and library.zip. Does this make > > sense? > > > > Dick > > > > > > > > > > ----------------------------------------------- > >-------------------------- Using Tomcat but need > > to do more? Need to support web services, > > security? Get stuff done quickly with > > pre-integrated technology to make your job > > easier Download IBM WebSphere Application > > Server v.1.0.1 based on Apache Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120 > >709&bid=263057&dat=121642 > > _______________________________________________ > > Py2exe-users mailing list > > Py2...@li... > > https://lists.sourceforge.net/lists/listinfo/py > >2exe-users > >------------------------------------------------------------------------- >Using Tomcat but need to do more? Need to support web services, security? >Get stuff done quickly with pre-integrated technology to make your job easier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >_______________________________________________ >Py2exe-users mailing list >Py2...@li... >https://lists.sourceforge.net/lists/listinfo/py2exe-users |
From: Werner F. B. <wer...@fr...> - 2006-08-31 10:43:26
|
Hi Dick, Dick Moores wrote: ... > Jim, > > I did take a look. If py2exe can figure out what a package needs to > work on Windows box-without-Python, and put them all into a folder > (dist?) ready to be zipped, please tell me how to use it that way. So > far, I haven't figured that out. > > Thanks, > > Dick Moores The following might be helpful for you to get a setup.py done for py2exe. The samples (just run a setup.py and have a look in the dist it creates): ..\Python24\Lib\site-packages\py2exe\samples and: http://www.py2exe.org/ http://www.py2exe.org/index.cgi/GeneralTipsAndTricks http://www.py2exe.org/index.cgi/WorkingWithVariousPackagesAndModules If you want to have a very nice distribution on Windows then you should package up your exe (and supporting files) with an installer (e.g. InnoSetup) which will guide your users through the installation. Werner |
From: Dick M. <rd...@rc...> - 2006-09-01 08:36:25
|
At 10:19 AM 8/31/2006, Werner F. Bruhin wrote: > I think most of the time developers only go to >the trouble of py2exe and installer stuff for an application or a >"suite" of scripts. > > > Yes, I'll have to learn to do that. I'll first get InnoSetup. From >http://www.jrsoftware.org/isinfo.php, right? How about NSIS? >(<http://nsis.sourceforge.net/Main_Page>)? > >I use InnoSetup, don't have any experience with NSIS but it seems to be >popular. > >Inno links I use are: >http://www.innosetup.com/ > >I would use the Quick Start pack which includes ISTool a GUI to creating >the install scripts. >http://www.jrsoftware.org/isdl.php#qsp I downloaded InnoSetup, and ISTool, but I just don't see exactly how to use them. I have a small, but I think useful app that I'd like to package up. I've used py2exe to create the dist folder containing the exe and a few other files. Here's a screen shot of dist, to which I've given the name of the app, "frac": <http://www.rcblue.com/Python/fracFolder.png>. I've read the help for InnoSetup and ISTool, but I just don't get what to do for what should be a simple package. Could someone (Werner?) get me started? I'd greatly appreciate it. Sorry to be so dumb. Or if it's thought that NSIS would be better, or easier for what I want to do, I have installed that as well. Thanks, Dick Moores |
From: Leeuw v. d. T. <tim...@nl...> - 2006-09-01 10:11:01
|
Dick, Look at the examples coming with py2exe, look at the examples on the py2exe homepage -- it all is spelled out for you there, really. I haven't yet created an installer from py2exe but with the examples I've seen I'm confident I could do it with no pain. So I'm sure that you should be able to do so as well, if you just take a proper look at those samples and play with them, try them out, and try to port them over to your own project. Just try something out, and you should get the hang of it -- that's my advise to you here! Cheers, --Tim -----Original Message----- From: py2...@li... [mailto:py2...@li...] On Behalf Of Dick Moores Sent: vrijdag 1 september 2006 10:36 To: py2...@li...> Subject: [Py2exe-users] Use of installer (Was: basic setup.py problem) At 10:19 AM 8/31/2006, Werner F. Bruhin wrote: > I think most of the time developers only go to >the trouble of py2exe and installer stuff for an application or a >"suite" of scripts. > > > Yes, I'll have to learn to do that. I'll first get InnoSetup. From >http://www.jrsoftware.org/isinfo.php, right? How about NSIS? >(<http://nsis.sourceforge.net/Main_Page>)? > >I use InnoSetup, don't have any experience with NSIS but it seems to be >popular. > >Inno links I use are: >http://www.innosetup.com/ > >I would use the Quick Start pack which includes ISTool a GUI to creating >the install scripts. >http://www.jrsoftware.org/isdl.php#qsp I downloaded InnoSetup, and ISTool, but I just don't see exactly how=20 to use them. I have a small, but I think useful app that I'd like to=20 package up. I've used py2exe to create the dist folder containing the=20 exe and a few other files. Here's a screen shot of dist, to which=20 I've given the name of the app, "frac":=20 <http://www.rcblue.com/Python/fracFolder.png>. I've read the help for=20 InnoSetup and ISTool, but I just don't get what to do for what should=20 be a simple package. Could someone (Werner?) get me started? I'd=20 greatly appreciate it. Sorry to be so dumb. Or if it's thought that NSIS would be better, or easier for what I=20 want to do, I have installed that as well. Thanks, Dick Moores ------------------------------------------------------------------------ - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D= 121642 _______________________________________________ Py2exe-users mailing list Py2...@li... https://lists.sourceforge.net/lists/listinfo/py2exe-users |
From: Werner F. B. <wer...@fr...> - 2006-08-31 17:20:23
|
Dick, Please copy the list (Reply All on some e-mail clients), for the archive. Dick Moores wrote: > At 03:43 AM 8/31/2006, Werner F. Bruhin wrote: > >> Hi Dick, >> >> The following might be helpful for you to get a setup.py done for py2exe. >> >> The samples (just run a setup.py and have a look in the dist it creates): >> ..\Python24\Lib\site-packages\py2exe\samples > > > Most require something I don't have yet, such as wxPython, but I did use my old setup.py on a lot of different scripts of mine, and now think I see what's going on. py2exe DOES work! Yep it does, I use it for my shareware application, depending on what libraries one uses it can take a bit to get it to work, but this is most often due to the fact that the library developers use "non standard" ways to import things. I think most of the time developers only go to the trouble of py2exe and installer stuff for an application or a "suite" of scripts. > > Yes, I'll have to learn to do that. I'll first get InnoSetup. From http://www.jrsoftware.org/isinfo.php, right? How about NSIS? (<http://nsis.sourceforge.net/Main_Page>)? I use InnoSetup, don't have any experience with NSIS but it seems to be popular. Inno links I use are: http://www.innosetup.com/ I would use the Quick Start pack which includes ISTool a GUI to creating the install scripts. http://www.jrsoftware.org/isdl.php#qsp > > Thanks very much. > > Dick Your welcome Werner > > > |
From: Werner F. B. <wer...@fr...> - 2006-09-01 10:14:58
Attachments:
frac.iss
|
Hi Dick, Dick Moores wrote: ... > I downloaded InnoSetup, and ISTool, but I just don't see exactly how > to use them. I have a small, but I think useful app that I'd like to > package up. I've used py2exe to create the dist folder containing the > exe and a few other files. Here's a screen shot of dist, to which > I've given the name of the app, "frac": > <http://www.rcblue.com/Python/fracFolder.png>. I've read the help for > InnoSetup and ISTool, but I just don't get what to do for what should > be a simple package. Could someone (Werner?) get me started? I'd > greatly appreciate it. Sorry to be so dumb. I attached a file (obviously not tested) which I created using the ISTool wizard (Menu option File/New - DO NOT click "Create a new empty script file") and follow the prompts (only manual change was to add "/ultra" to the compression option. Hopefully this gets you going. BTW, I would not keep my development stuff in the Python folder (just like to keep things nicely separated, makes backup etc easier), create e.g. a folder called "dev" and in it you have a sub folder for each project (Frac being one) with whatever sub folders which make sense for the particular project (e.g. source, setupscripts etc). Werner |
From: Dick M. <rd...@rc...> - 2006-09-04 00:58:40
|
At 03:12 AM 9/1/2006, Werner F. Bruhin wrote: >Hi Dick, > >Dick Moores wrote: >... >>I downloaded InnoSetup, and ISTool, but I just don't see exactly >>how to use them. I have a small, but I think useful app that I'd >>like to package up. I've used py2exe to create the dist folder >>containing the exe and a few other files. Here's a screen shot of >>dist, to which I've given the name of the app, "frac": >><http://www.rcblue.com/Python/fracFolder.png>. I've read the help >>for InnoSetup and ISTool, but I just don't get what to do for what >>should be a simple package. Could someone (Werner?) get me started? >>I'd greatly appreciate it. Sorry to be so dumb. >I attached a file (obviously not tested) which I created using the >ISTool wizard (Menu option File/New - DO NOT click "Create a new >empty script file") and follow the prompts (only manual change was >to add "/ultra" to the compression option. > >Hopefully this gets you going. Yes, it certainly did. Thank you taking the trouble to show a script that helped me see what I needed to do. >BTW, I would not keep my development stuff in the Python folder >(just like to keep things nicely separated, makes backup etc >easier), create e.g. a folder called "dev" and in it you have a sub >folder for each project (Frac being one) with whatever sub folders >which make sense for the particular project (e.g. source, setupscripts etc). Point well-taken (I should have taken a similar point made earlier by John Machin. I now have E:\dev. Dick |