py2exe

Mike Driscoll wrote:
> Hi,
> 
> I recently compiled a really simple wxPython application using GUI2exe / 
> py2exe and it works great on 4 machines, but gives me this error on 3 
> others:
> 
> Traceback (most recent call last):
>  File "TaxListCtrl.py", line 12, in <module>
>  File "zipextimporter.pyo", line 82, in load_module
>  File "wx\__init__.pyo", line 45, in <module>
>  File "zipextimporter.pyo", line 82, in load_module
>  File "wx\_core.pyo", line 4, in <module>
>  File "zipextimporter.pyo", line 98, in load_module
> ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd
> 
> I'm using the option to bundle it all into a single file. The operating 
> system is Windows XP. I'm using wxPython 2.8.8.0, Python 2.5 and py2exe 
> 0.6.8. I tried py2exe 0.6.6 first. The last time this happened, it was 
> because I hadn't included "msvcp71.dll", but I didn't forget that this 
> time. Any hints are appreciated  Thanks a lot!
> 
> Mike
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/

Try it with bundle = 3, then bundle = 2.  Some dlls don't seem to be able to be 
run from the .exe.  I NEVER use bundle = 1 and zipfile = None.  It just isn't 
worth it.

-Larry

Larry Bates wrote:
> Mike Driscoll wrote:
>   
>> Hi,
>>
>> I recently compiled a really simple wxPython application using GUI2exe / 
>> py2exe and it works great on 4 machines, but gives me this error on 3 
>> others:
>>
>> Traceback (most recent call last):
>>  File "TaxListCtrl.py", line 12, in <module>
>>  File "zipextimporter.pyo", line 82, in load_module
>>  File "wx\__init__.pyo", line 45, in <module>
>>  File "zipextimporter.pyo", line 82, in load_module
>>  File "wx\_core.pyo", line 4, in <module>
>>  File "zipextimporter.pyo", line 98, in load_module
>> ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd
>>
>> I'm using the option to bundle it all into a single file. The operating 
>> system is Windows XP. I'm using wxPython 2.8.8.0, Python 2.5 and py2exe 
>> 0.6.8. I tried py2exe 0.6.6 first. The last time this happened, it was 
>> because I hadn't included "msvcp71.dll", but I didn't forget that this 
>> time. Any hints are appreciated  Thanks a lot!
>>
>> Mike
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>     
>
> Try it with bundle = 3, then bundle = 2.  Some dlls don't seem to be able to be 
> run from the .exe.  I NEVER use bundle = 1 and zipfile = None.  It just isn't 
> worth it.
>
> -Larry
>
>   

I tried bundle=3 soon after sending my email and it did work. However, 
that brings up a second question. Why does bundle=3 always result in 
more than three files in the dist directory? I get 17!. It's not a big 
deal since I can just use Inno Setup to wrap them all up if I need to, 
but I think the "3" is a little mis-leading.

Thanks for the tip!

Mike

Mike Driscoll schrieb:
> Larry Bates wrote:
>> Try it with bundle = 3, then bundle = 2.  Some dlls don't seem to be able to be 
>> run from the .exe.  I NEVER use bundle = 1 and zipfile = None.  It just isn't 
>> worth it.
>>
> 
> I tried bundle=3 soon after sending my email and it did work. However, 
> that brings up a second question. Why does bundle=3 always result in 
> more than three files in the dist directory? I get 17!. It's not a big 
> deal since I can just use Inno Setup to wrap them all up if I need to, 
> but I think the "3" is a little mis-leading.

The value you give to the bundle option is a flag, not the number of files you want.

Thomas

Thomas Heller wrote:
> Mike Driscoll schrieb:
>   
>> Larry Bates wrote:
>>     
>>> Try it with bundle = 3, then bundle = 2.  Some dlls don't seem to be able to be 
>>> run from the .exe.  I NEVER use bundle = 1 and zipfile = None.  It just isn't 
>>> worth it.
>>>
>>>       
>> I tried bundle=3 soon after sending my email and it did work. However, 
>> that brings up a second question. Why does bundle=3 always result in 
>> more than three files in the dist directory? I get 17!. It's not a big 
>> deal since I can just use Inno Setup to wrap them all up if I need to, 
>> but I think the "3" is a little mis-leading.
>>     
>
> The value you give to the bundle option is a flag, not the number of files you want.
>
> Thomas
>
>   
Ah. Next time I will read the docs more closely rather than assuming. 
Sorry. I'm still pretty green when it comes to using py2exe.

Mike

Larry Bates wrote:
> bundle = 3 doesn't mean 3 files it means don't bundle.
>
> Maybe this will help from docs:
>
> The bundle option
>
> By default py2exe creates these files in the dist directory which you must
> deploy:
>
>        1. One (or more) .exe files
>        2. The python##.dll
>        3. A couple of .pyd files which are the compiled extensions that the exe
> files need, plus any other .dll files that the extensions need.
>        4. A library.zip file which contains the compiled pure python modules as
> .pyc or .pyo files (if you have specified 'zipfile=None' in the setup script
> this file is append to the .exe files and not present in the dist-directory).
>
> The --bundle <level> or -b <level> command line switch will create less files
> because binary extensions, runtime dlls, and even the Python-dll itself is
> bundled into the executable itself, or inside the library-archive if you prefer
> that.
>
> The bundled pyds and dlls are never unpacked to the file system, instead they
> are transparently loaded at runtime from the bundle. The resulting executable
> appears to be statically linked.
>
> Specifying a level of 2 includes the .pyd and .dll files into the zip-archive or
> the executable. Thus, the dist directory will contain your exe file(s), the
> library.zip file (if you haven't specified 'zipfile=None'), and the python dll.
> The advantage of this scheme is that the application can still load extension
> modules from the file system if you extend sys.path at runtime.
>
> Using a level of 1 includes the .pyd and .dll files into the zip-archive or the
> executable itself, and does the same for pythonXY.dll. The advantage is that you
> only need to distribute one file per exe, which will however be quite large.
> Another advantage is that inproc COM servers will run completely isolated from
> other Python interpreters in the same exe. The disadvantage of this scheme is
> that it is impossible to load other extensions from the file system, the
> application will crash with a fatal Python error if you try this. I have still
> to find a way to prevent this and raise an ImportError instead - any suggestions
> how this can be implemented would be very welcome.
>
> The bundle-option has been tested with some popular extensions, but of course
> there's no guarantee that any extension will work in bundled form - be sure to
> test the executable (which you should do anyway).
>
> The bundle option achieves its magic by code which emulates the Windows
> LoadLibrary api, it is compiled into the exe-stubs that py2exe uses. For
> experimentation, it is also installed as a normal Python extension _memimporte
>
> -Larry
>
>   

<snip>

Wow! That's a lot of information. I understand py2exe somewhat better 
now. I'm not sure where you learn about things like the LoadLibrary api 
and such, but it's good to know the nomenclature. Hopefully I will be 
able to make more informed questions next time.

Thanks again!

Mike

Hi Mike,

On Sat, Aug 2, 2008 at 4:17 AM, Mike Driscoll wrote:
> Larry Bates wrote:
>> bundle = 3 doesn't mean 3 files it means don't bundle.
>>
>> Maybe this will help from docs:
>>
>> The bundle option
>>
>> By default py2exe creates these files in the dist directory which you must
>> deploy:
>>
>>        1. One (or more) .exe files
>>        2. The python##.dll
>>        3. A couple of .pyd files which are the compiled extensions that the exe
>> files need, plus any other .dll files that the extensions need.
>>        4. A library.zip file which contains the compiled pure python modules as
>> .pyc or .pyo files (if you have specified 'zipfile=None' in the setup script
>> this file is append to the .exe files and not present in the dist-directory).
>>
>> The --bundle <level> or -b <level> command line switch will create less files
>> because binary extensions, runtime dlls, and even the Python-dll itself is
>> bundled into the executable itself, or inside the library-archive if you prefer
>> that.
>>
>> The bundled pyds and dlls are never unpacked to the file system, instead they
>> are transparently loaded at runtime from the bundle. The resulting executable
>> appears to be statically linked.
>>
>> Specifying a level of 2 includes the .pyd and .dll files into the zip-archive or
>> the executable. Thus, the dist directory will contain your exe file(s), the
>> library.zip file (if you haven't specified 'zipfile=None'), and the python dll.
>> The advantage of this scheme is that the application can still load extension
>> modules from the file system if you extend sys.path at runtime.
>>
>> Using a level of 1 includes the .pyd and .dll files into the zip-archive or the
>> executable itself, and does the same for pythonXY.dll. The advantage is that you
>> only need to distribute one file per exe, which will however be quite large.
>> Another advantage is that inproc COM servers will run completely isolated from
>> other Python interpreters in the same exe. The disadvantage of this scheme is
>> that it is impossible to load other extensions from the file system, the
>> application will crash with a fatal Python error if you try this. I have still
>> to find a way to prevent this and raise an ImportError instead - any suggestions
>> how this can be implemented would be very welcome.
>>
>> The bundle-option has been tested with some popular extensions, but of course
>> there's no guarantee that any extension will work in bundled form - be sure to
>> test the executable (which you should do anyway).
>>
>> The bundle option achieves its magic by code which emulates the Windows
>> LoadLibrary api, it is compiled into the exe-stubs that py2exe uses. For
>> experimentation, it is also installed as a normal Python extension _memimporte
>>
>> -Larry
>>
>>
>
> <snip>
>
> Wow! That's a lot of information. I understand py2exe somewhat better
> now. I'm not sure where you learn about things like the LoadLibrary api
> and such, but it's good to know the nomenclature. Hopefully I will be
> able to make more informed questions next time.

You can get all the docs, switches and py2exe options help even from
GUI2Exe, by choosing the menu "View" ==> "Compiler Switches". This
will open a web browser window in which all (or almost alll) the
py2exe switches are explained.

HTH.

Andrea.

"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/